Welcome!
Story
2 min read
24 · he/him · Aswan, Egypt
I started in computer science, but motion design came first — years of remote work with motion studios. Animation was my first language for how things should feel on a screen.
About two years shipping production frontend. Much longer making things move.
The problem was that my animations looked good in a reel and dead once they landed. No response, no state, no back-and-forth with the user. I tried Rive. It got close, but I still couldn't own the full interactive loop the way I wanted.
I went looking for a medium where motion and interaction could live in the same place. React and the ecosystem around it was the first time that clicked. I mapped my own path from motion into frontend.
On the web, that eye shows up in interaction how things respond, settle, and hold up under real constraints. I care about interfaces that feel alive, not just look finished in a screenshot.
How I work
I don't start a project by outsourcing the thinking — not to tools, templates, or whatever stack is trending this month. I start with what's actually being built: who uses it, what has to feel fast, what will probably change in six months, and where users are so performance isn't an afterthought.
Once that's clear, I pick a stack I can shape — usually Next.js, TypeScript, and Tailwind — but the stack is never the point. Flexibility is. I want to read the UI layer, change it when design shifts, and not fight a black box when requirements move.
Motion, responsiveness, and accessibility aren't a final pass for me. They're part of the first draft, because that's where products start to feel considered instead of assembled.