Writing
Practical write-ups from real projects: Flutter architecture, WebGL frame budgets on mid-range Android, and the Next.js SEO checklist I run before every launch.
Featured · · 10 min read
No Figma file, no research spiral, just one working day of 8 to 10 hours. Here is the hour-by-hour build log for an animation-heavy portfolio directed through AI, including the contrast bug and the SEO pass at midnight.
GSAPNext.jsAI-Assisted Build
· 11 min read
Metadata is the easy part. This is the checklist I actually run on a Next.js App Router build before it goes live, including the parts most teams skip because a plugin used to do them.
Next.jsSEOCore Web Vitals
· 10 min read
A scene that runs at 120fps on a laptop can drop to 22fps on a three year old Android phone. Here is the frame budget I use, and the order I cut things in when a WebGL build starts to stutter.
Three.jsWebGLPerformance
Coming up
Practical write-ups instead of hot takes - each one tied to code from these projects.
State management that survives scale, offline-first data and testable widget architecture.
How to keep Three.js and GSAP scenes at 60fps on mid-range Android devices.
Structured data, Core Web Vitals and content architecture that compounds over time.
Or browse the projects in the meantime.
Open for projects, collaborations and virtual coffee chats. Send the technical requirements, Figma drafts, or napkin sketch, and I will reply with an architectural breakdown, realistic milestone roadmap, and high-impact execution plan.
