From Designer to Full-Stack: My Flutter + Next.js Journey
I started in Photoshop. Now I ship apps. The path wasn't a bootcamp — it was building things I actually needed.
By Tharaka Jay · September 5, 2026 · 8 min read
People assume I did a computer science degree or a bootcamp. I didn't. I'm a designer who got tired of handing mockups to developers and watching the details die in translation. So I learned to build — first the web, then mobile.
Why Next.js first
Next.js was the natural first step because I already thought in pages and components from design tools. The App Router, server components, and file-based routing map cleanly onto how a designer structures a site. My LPL Concept project — Next.js, Node, MongoDB, Tailwind — was the project where it all clicked.
Why Flutter second
Flutter won because of one codebase for Android, iOS and web. FuelMap Sri Lanka — live fuel availability at stations across the island — forced me to learn the hard parts properly: state management, offline handling, push notifications, and maps. Nothing teaches like an app real people depend on.
What being both actually buys you
- Designs that respect engineering constraints — no impossible animations in the mockup.
- Faster shipping — no handoff meetings, no translation loss.
- Better UX instincts — you feel the cost of every extra screen because you have to build it.
- Client trust — one person accountable for the whole thing.
Learn to build what you design and your designs get better. Learn to design what you build and your code gets better.
