Designing with No-Code: A Developer’s Perspective
From Code to Canvas
I started out learning to code—HTML, CSS, JavaScript, the whole lot. I used to think being "technical" meant doing everything manually. But after months of writing syntax from scratch, I realised that what I really wanted was momentum. When I discovered no-code tools like Framer, it changed everything. It wasn’t a shortcut—it was a shift in mindset. No-code didn’t erase my logic skills; it amplified them.
Developer Thinking, Design Execution
Even in Framer, I still approach projects like a developer. I think in systems. I create reusable components. I pay attention to performance and structure. But the difference now is that I can build faster and more visually—seeing changes unfold live, testing ideas immediately, and iterating without friction. That agility makes me more effective, not less technical.
Why It Works for Me
I don’t write much code anymore—and I’m okay with that. Framer has become the core of my workflow, letting me design and build with freedom and clarity. But I haven’t turned my back on code. It’s simply taken a back seat while I grow my expertise in other areas such as better design and a deeper understanding how no-code works
I still believe there’s value in understanding both design and development. But right now, I’m focused on creating with the tools that let me move fast, iterate freely, and build experiences that feel truly thoughtful.




