Why I Built All 170 Tools to Run in the Browser (And What I Learned)
The article discusses the author's decision to build 170 tools that run entirely in the browser, avoiding server-side processing. This approach addresses privacy concerns associated with uploading sensitive documents to third-party servers. While client-side processing has its limitations, the author believes the trade-offs are worthwhile for most users.
- ▪The author built UtilVox to process files directly in the browser, ensuring user privacy.
- ▪Client-side processing has limitations such as memory constraints and slower processing speeds for heavy operations.
- ▪The author emphasizes the importance of shipping tools quickly and building in public to engage users.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/utilvox/why-i-built-all-170-tools-to-run-in-the-browser-and-what-i-learned-pa4 |
| Publication time | Mon, 18 May 2026 17:00:11 +0000 |
| Retrieval time | 2026-05-18T17:04:56.667Z |
| Last seen | 2026-05-18T17:04:56.667Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | GMIEF4J7af_T |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3938528) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } UtilVox Posted on May 18 Why I Built All 170 Tools to Run in the Browser (And What I Learned) #webdev #javascript #nextjs #buildinpublic Why I Built All 170 Tools to Run in the Browser When I started building UtilVox, the obvious approach was server-side processing. Upload file → process on server → return result. Every major tool site works this way. I went the opposite direction. Here's why — and what I learned.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
