What I learned shipping it.
Essays on frontend engineering, React Native, payments and livestreaming, written from real projects.
5 posts
Migrating a Bootstrap Codebase to Tailwind Without a Big-Bang Rewrite
Running both side by side, isolating the CSS reset conflict, and knowing when to stop migrating.
React Query on Web and Mobile: Same Cache, Different Rules
Stale times, background refetching, and offline behavior that made sense on desktop and felt broken on a phone.
One Product Brain, Two Clients: Next.js and React Native
How much you can genuinely share between web and mobile, and where forcing it starts to cost more than it saves.
Designing an API You’ll Have to Consume Yourself
Building both sides changes the endpoints you write. Here are a few habits I picked up from being my own worst client.
From Laravel Monolith to Next.js Frontend
For years, Laravel monoliths were my go-to solution for building web applications. They were fast to develop, easy to maintain, and perfect for small to medium-sized projects. But as applications grew in complexity, I found myself moving toward a decoupled architecture with Laravel as the backend and Next.js as the frontend. This post shares why I made the transition, the challenges I faced, and the lessons I learned along the way.