DEV Community

Cover image for Why I built a zero-backend developer utility suite using Next.js and Web Workers
Yasser Al-ariqi
Yasser Al-ariqi

Posted on

Why I built a zero-backend developer utility suite using Next.js and Web Workers

Most online utility sites have a major flaw: they secretly upload your clipboard data, cURL requests, and JWTs to backend server logs just to format or parse them.

To solve this privacy issue, I built DevDock (https://getdevdock.com) — a browser-only suite of 30+ developer tools where zero data leaves your machine.

Architecture and Key Learnings

1. Heavy tasks off the main thread

Parsing large JSON payloads (10MB+) or running code formatters usually locks up the browser UI. I moved heavy processing into Web Workers so the UI stays responsive at 60fps.

2. In-browser execution engines

Instead of relying on server APIs, everything runs client-side:

  • Code formatting via @prettier/standalone running in a Web Worker
  • LLM token calculations via @lenic/tiktoken
  • Image conversions via browser Canvas API

3. Main tools live right now

  • Text Diff Tool (100% private comparison)
  • QR Code Generator
  • JSON Formatter & Tree Viewer
  • JWT Decoder
  • cURL to Code Converter
  • CSS to Tailwind Converter

Check it out at https://getdevdock.com and let me know how the client-side performance feels on your machine!

Top comments (1)

Collapse
 
yasser_alariqi_98794255c profile image
Yasser Al-ariqi •

If anyone is working with client-side Web Workers in Next.js App Router, how are you handling memory cleanup when users rapidly transition routes? Would love to hear how others approach worker lifecycles!