Projects

The build behind each one — the problem it solved, the tradeoffs, and what I'd change. Every card links through to something running: the browser tools live in the Lab, and Praxis, Build Components, the Motion Lab and Pare run on their own domains.

projects
14● all live
browser tools
11
web apps
3
standalone apps
4
  • LiveTool · 2026

    Pare — Asset Optimization That Runs in the Browser

    A browser-only optimizer for images, fonts and code: real codecs compiled to WebAssembly, no upload, no install, and a hard rule against any change that could break your site.

    • Runs entirely client-side: WebAssembly codecs in a worker pool, no server to send files to, and offline after first use
    • Images: a resize ladder encoded to AVIF, WebP and an optimized original, ThumbHash placeholders, and a paste-ready <picture> tag with width and height to prevent layout shift
    • Fonts: split by writing system so a page loads only the scripts it uses, or subset to the characters it shows — WOFF2 with @font-face and unicode-range
    • Whole-site mode fingerprints only files whose every reference could be traced, rewrites the addresses, then renders each page before and after — no clean comparison, no download

What it's built with

Counted from the project files above, not picked for effect. The same few tools keep showing up because I would rather know them well than collect new ones.

  • TypeScript14 of 14
  • Next.js13 of 14
  • Tailwind CSS9 of 14
  • React4 of 14
  • Playwright2 of 14
  • SVG2 of 14
  • Vite1 of 14
  • WebAssembly1 of 14

Want to use something?

The browser tools run in the Lab, no signup.

FAQ

Frequently asked questions

What the case studies are, and are not.

4 questions

Not answered here?

Ask directly. I reply within 24 hours.

Ask a question →
Are these client projects?

No. Everything on this page is something I built myself, and each case study says what it is and is not. Praxis, for example, has no users and I do not report numbers I do not have.

Were these built with AI assistance?

Where it applies, the case study says so. Praxis states that the implementation was built with AI assistance that I directed and reviewed, while the product thinking, learning model and UX are mine.

Which projects can I try right now?

The browser tools run in the Lab with no signup. Praxis, Build Components, the Motion Lab and Pare run on their own domains, linked from each card.

Where is the source code?

Projects with a public repository show a GitHub link on their card and in the detail panel.

Open now · reply within 24 hours

Like what you see? Let’s build yours.

I take on freelance and contract frontend work, remote, for clients worldwide.

Prefer email? hello@devstash.me

What happens next

  1. 1

    You write

    A few lines on the goal, the deadline and where the traffic comes from.

  2. 2

    I reply within 24 hours

    With questions, or a quote if the scope is already clear.

  3. 3

    We agree the scope

    A written scope and a fixed quote before any work starts.