Back to archive
Web & PlatformsUtility SoftwareNext.js + WebAssemblyReusable browser-native utility OS

Exhibition page

Attnom Tools: utility OS

A free, browser-native suite of file, image, OCR, and archive utilities that work entirely client-side.

Utility count

20+

The product grew into a true utility estate rather than a small set of isolated experiments.

Privacy model

Browser-native

Files stay on-device, which becomes both a user promise and a platform constraint that shaped the architecture.

Reuse model

Shared primitives

A shared workbench, queue, and result pattern makes each new tool faster to ship and easier to learn.

web

What this case covers

Utility SoftwareStack focus: Next.js + WebAssemblyOutcome focus: Reusable browser-native utility OSService: Explore practical toolsTool: Tools dockPublic reference build

Next step

Use the tools dock when you want to inspect how the shared utility grammar behaves across the live product experience.

Exhibition notes

Industry: Utility Software

Related: Explore practical tools / Tools dock

Outcome: One design grammar now powers many privacy-first utilities without fragmenting the user experience.

This exhibition can be used as a public reference for similar work.

Chapter 01

Challenge

01

Build a fast browser utility that rivals desktop software, stays private, and avoids unnecessary server cost.

Chapter 02

System

02

Workbench shell with shared file queue, control rail, and progress states.

WASM-backed engines for OCR (Tesseract), PDF (pdf-lib), media (FFmpeg), and archives (zip.js).

Mobile-first launcher with deck/studio split and progressive deck batching.

Chapter 03

Interface

03

Primary capabilities: Utility Engine, Mobile-First UX, WASM Pipelines.

Signature stack markers: Next.js, WebAssembly, pdf-lib, Tesseract.js.

web

Annotation

Utility Engine

Annotation

Mobile-First UX

Annotation

WASM Pipelines

Chapter 04

Outcome

04

20+ tools across documents, images, video, OCR, and archives shipped.

Zero server processing for user files: privacy stays at the browser layer.

Single component shape powers every tool, reducing maintenance cost.

map

One workbench, many everyday jobs

The same familiar flow works across documents, images, OCR, media, and archives.

Documents

PDF, text, and OCR tools share a predictable queue, export flow, and private browser processing.

Media

Image and video tools use the same simple rhythm: import, change, preview, export.

Archives

Batch extraction and compression belong in the same private workbench instead of another disconnected app.

Paid expansion

The shared experience makes larger limits and bundles easy to add without confusing free users.

In short

Shared system

The case shows how one utility platform can support documents, images, OCR, media, and archive work from the same shell.

Shared queue logic

One pattern

Import, progress, export, and status behavior now travel across many tool families.

Delivery leverage

New tools ship faster

The platform can add new utilities without designing or engineering a fresh shell from scratch.

Monetization lesson

Value layered cleanly

Free and premium utility behaviors can now coexist inside one coherent product grammar.

Related archive drawer

Choose the next step that fits this case.

Try the tools