Amory.dev
What I do

Full-stack, end to end — from the database to the App Store.

I'm a generalist who ships. Most of what I build, I also run: a rewards network, an AI assistant, a POS, a game. That means owning everything from the data model to the support inbox.

Areas

Full-stack web

Production web apps and portals end to end: schema, API, auth and roles, admin tooling, payments, and the front end on top. Mostly Next.js and TypeScript on Postgres.

Mobile

Cross-platform apps with Expo and React Native, shipped through App Store review and TestFlight. Native iOS capabilities where the product needs them, like on-device speech recognition.

Point-of-sale & hardware

A white-label POS running on the phones and tablets businesses already own: register, catalog, tax, reporting, receipts, and offline-first on-device storage.

AI products

LLM features built into real products: agents with tool use, long-term memory, structured extraction from free-form speech and text. Mostly on Claude.

Open-source desktop tools

Small, sharp utilities for my own Linux setup (Hyprland and Omarchy) in Rust, QML, and shell: smart-home control, screen-recording overlays, webcam head-tracking. Released on GitHub.

Product & design

I run my own products, so I own the whole loop: scoping, interface design, launch, support, and the next iteration. Editorial design that doesn't look like a template.

Stack

TypeScriptRustNext.jsReactReact Native / ExpoSupabase / PostgresSQLiteTurborepo + pnpmClaude APIMapboxRevenueCatResendPayPalPhaser 3QMLShell / systemdLinux / HyprlandVercel

How I work

01
Understand the problem
Start from what people actually do every day, not from the tool. The scope goes on paper before the code does.
02
Ship early
A working preview from week one, then small, frequent releases. Feedback on something real beats feedback on a mockup.
03
Own it in production
Monitoring, migrations, app review, support. I treat launch as the start of the job, because for my own products it is.
04
Leave it clean
Typed code, documented handoffs, and data that belongs to whoever owns the product.

See it in practice

Case studies cover what each product does, how it's built, and the hard parts.

View the work