Suheb This looks like a useful approach, especially keeping the QR generation fully client-side. Using Next.js 16 should also make it easier to keep the toolkit fast and lightweight. The focus on privacy is a nice touch since users don't need to upload their QR data to a server.
Kris Dev Thanks! That was exactly the goal. I wanted the core QR workflow to stay fully client-side so users can generate, style, and export their QR codes without sending the payload to a backend. It also keeps the architecture simple and lightweight, which fits well with the kind of utility I want QR Forge to be. Appreciate the feedback!
Abhivarde show some love on X 🖤 https://x.com/varde_abhi/status/2092246715747455308
Abhivarde shipped an update to gitphere, a globe that maps a GitHub user's following list by location. ↳ now installs as a shadcn component ↳ drop it straight into any Next.js project ↳ your own GitHub token, your own server, no dependency on mine https://x.com/varde_abhi/status/2093577937975136414