Don’t animate keyboard-initiated actions.
As an example, I use Raycast hundreds of times a day. If it animated every time I opened it, it would make it feel slow, delayed, and disconnected from my actions.
But there’s no animation at all. That’s the optimal experience.
I think this is worth some nuance.
In recent history, many companies have employed 'product designers' whose primary activity and output has been the creation of software interface facsimiles, e.g. mockups in a drawing tool like Figma.
Those making mockups have of course been doing more than just that, to varying extents leading or more commonly participating in the process of deciding what to build and why. But there was value in that tangible output itself.
I think @gokulr is directionally correct that the role of someone whose primary output is the creating of an interface mockup is quickly disappearing.
But the role of someone who figures out what needs to exist, why, how it should work, how it should should be positioned, differentiated and made memorable has never been more in demand.
I speak with founders on a near weekly basis (many of them in Gokul's own portfolio) desperate for this kind of person.
His conclusions though I agree with almost entirely:
there will always be an opportunity to specialize in the creation of visual interfaces, but more broadly most product designers who want to be employees (totally fine) should take on more responsibilities that have historically been done by PMs or Engineers, to varying degrees.
From my POV, this is just what a product designer is and what we should have been doing the whole time, but that's another post.
designers are dead. figma is dead. ai ate your job. design is over. bruuuuuuh, every two weeks, same shitposts. my block button has never been busier.
meanwhile: for the first time in 12 years the tools actually keep up with my thinking. iterate in minutes, explore 10 directions where before you had energy for two, create design tool by yourself. the golden era of design isn’t coming. it started. express your vision and create something new, bro
(maybe social media content is dead? asking for the guys writing “design is dead” every two weeks lol)
Use 𝚜𝚒𝚋𝚕𝚒𝚗𝚐-𝚒𝚗𝚍𝚎𝚡() to stagger children of a parent without having to manually track a using --𝚒 𝚟𝚊𝚛𝚒𝚊𝚋𝚕𝚎𝚜 or having to use an animation library
.𝚒𝚝𝚎𝚖 {
𝚊𝚗𝚒𝚖𝚊𝚝𝚒𝚘𝚗: 𝚎𝚗𝚝𝚎𝚛 𝟶.𝟺𝟻𝚜 𝚌𝚞𝚋𝚒𝚌-𝚋𝚎𝚣𝚒𝚎𝚛(𝟶.𝟸𝟸, 𝟷, 𝟶.𝟹𝟼, 𝟷) 𝚋𝚘𝚝𝚑;
𝚊𝚗𝚒𝚖𝚊𝚝𝚒𝚘𝚗-𝚍𝚎𝚕𝚊𝚢: 𝚌𝚊𝚕𝚌(𝟶.𝟷𝟸𝚜 * (𝚜𝚒𝚋𝚕𝚒𝚗𝚐-𝚒𝚗𝚍𝚎𝚡() - 𝟷));
}
@𝚔𝚎𝚢𝚏𝚛𝚊𝚖𝚎𝚜 𝚎𝚗𝚝𝚎𝚛 {
𝚏𝚛𝚘𝚖 {
𝚘𝚙𝚊𝚌𝚒𝚝𝚢: 𝟶;
𝚝𝚛𝚊𝚗𝚜𝚏𝚘���𝚖: 𝚝𝚛𝚊𝚗𝚜𝚕𝚊𝚝𝚎𝚈(𝟼𝚙𝚡);
}
𝚝𝚘 {
𝚘𝚙𝚊𝚌𝚒𝚝𝚢: 𝟷;
𝚝𝚛𝚊𝚗𝚜𝚏𝚘𝚛𝚖: 𝚝𝚛𝚊𝚗𝚜𝚕𝚊𝚝𝚎𝚈(𝟶);
}
}
Clean and minimal approach for stagger animations
I turned a lot of the information and functionality from oklch fyi into a skill.
It can convert your entire project, convert individual colors, generate palettes, check contrast and more.
https://t.co/zRCJt4DJmu
Introducing 𝚑𝚒𝚝-𝚊𝚛𝚎𝚊—a collection of @tailwindcss utility classes for expanding the hit area of interactive elements.
Small hit areas are a silent UX killer. One class fixes it.
Distributed via @shadcn registry - see link below.
It's time to bring Haptics to the web 🫨
Create custom tactile patterns with strengths + durations for your web interactions.
Make your app feel as good as it looks ✨
→ https://t.co/DGz9Eu6nto
I'm Boris and I created Claude Code. I wanted to quickly share a few tips for using Claude Code, sourced directly from the Claude Code team. The way the team uses Claude is different than how I use it. Remember: there is no one right way to use Claude Code -- everyones' setup is different. You should experiment to see what works for you!