Why I built a "Zero-Backend" dev toolset with Next.js 16 and Tailwind v4

Let’s be real: most " free " online tools for developers suck. You want to resize a quick image for a README or format a messy JSON config, and you're met with: Shady ads everywhere. "Please create an account to download." The "Security Guilt"—waiting for a server to process your private data. I got tired of this friction. I wanted something that felt like a native app but lived in my browser. So, I spent the last few weeks building noserver.app. The Goal: 100% Client-Side The main challenge was: can I make heavy tasks (like image optimization or PDF manipulation) run entirely on the user's hardware? Thanks to WebAssembly (WASM) and the Canvas API, the answer is a resounding yes. The Stack (The "Vibe" part) I decided to go with the bleeding edge because... why not? Next.js 16 : The App Router is finally feeling stable, and the hydration handling in 16 is a lifesaver for WASM-heavy sites. Tailwind v4 : I switched to v4 early on, and the build speed is actually insane. No more bulky tail