Designing interfaces that feel alive
Motion is information. The 200ms rule, optimistic UI, and why restraint beats spectacle, notes from building the sticker wall you're reading this on.
Motion is information. The 200ms rule, optimistic UI, and why restraint beats spectacle, notes from building the sticker wall you're reading this on.
Two apps can do the same thing and feel completely different. One feels instant and intentional; the other feels like it's thinking about it. The difference is rarely performance, it's feedback. Interfaces that feel alive tell you what's happening, constantly, in small ways.
Every animation should answer a question: where did that come from, where did it go, did my action work? A button that presses down into its shadow says 'I heard you'. A card that lifts on hover says 'I'm interactive'. A page that fades in says 'this just arrived'. Decoration that answers no question is noise.
Humans perceive feedback under ~200ms as instant. Above that, they start wondering. Three techniques keep you under the line:
The fastest way to make an interface feel dead is to animate everything. If every element bounces, nothing does. I keep a short list of allowed motions, reveals on scroll, lifts on hover, one marquee, one draggable thing, and everything else stays still. Restraint is what makes the allowed motions read as intentional.
Note
Always honor prefers-reduced-motion. Alive for most users means calm for the users who need calm, same interface, no motion, no information lost.
This portfolio is my current answer to all of the above: thick outlines and hard shadows for tactility, doodles for warmth, and exactly one thing you can grab and throw around. If it feels alive, that's the design working.
Daniel Oluwadare · Emerald
Software engineer on TestFlow, and the person writing everything here. I build in public and post what I learn.
14 Nov 2026 · 3 min
Why my GitHub bot moved from WhatsApp to Telegram
A bot that pipes GitHub events into a chat I actually read. The WhatsApp version worked; Telegram made it maintainable. Here's the trade, and the architecture underneath.
10 Nov 2026 · 2 min
Building Calder: why I started a developer-first email API
Every project I shipped needed transactional email, and every time I wired up a provider I rebuilt the same three things. Calder is my attempt to build them once, properly.
6 Nov 2026 · 4 min
Building TestFlow: what a real exam backend taught me about users
1,500+ questions, 1,300+ students, and a lecture timetable that does not care about my deploy schedule. The backend decisions that made TestFlow survive contact with real students.