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

Source: Dev.to

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

Thanks to WebAssembly (WASM) and the Canvas API, the answer is a resounding yes.

The Stack (The “Vibe” part)

• 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 – Switched early; build speed is insane. No more bulky tailwind.config.js—everything is CSS‑first, making the styling phase actually fun.
• Pica.js – Provides high‑quality image resizing without that “browser blur.”

What I Learned

Managing WASM binaries in a Next.js environment is still a bit of a headache; matching the server/client chunks can be tricky.

What’s Next?

I have two questions for the community:

1. What’s a “simple” tool you use that feels unnecessarily bloated or slow?
2. If you’ve worked with Tailwind v4, how are you handling complex animations? I’m still figuring out the best patterns there.

Check it out here: 🚀

I’d love some brutal feedback on the performance and the UI. No filters—just tell me what’s broken.