The path from Flutter experiments to product-minded frontends.

I first found Flutter because I loved the idea of one codebase delivering the same care across multiple platforms. That quickly turned into a deeper curiosity about systems, motion, and the small product details that make software feel trustworthy.

Since then I have focused on building mobile-first experiences with clear architecture, reliable state management, and UI that feels editorial instead of mechanical. I care about pacing, whitespace, and interfaces that speak like a real person.

Lately I have been translating that same mindset into the web, using React and Next.js with the same discipline I bring to Flutter: component boundaries, shared design tokens, and code that teaches through its structure.