iOS + product execution
Native app flows, progression systems, store operations, notifications, and release-minded UX.
From iOS apps and game mechanics to backend systems, production infrastructure, and AI-assisted workflows, the work here is meant to run in the real world — not just look convincing in a mockup.
I like the messy middle: integrating product decisions, implementation detail, and operations until the thing is actually useful.
Native app flows, progression systems, store operations, notifications, and release-minded UX.
APIs, persistence, session state, notes/attachments, and the operational details that make products hold together.
VPS provisioning, Docker Compose, Caddy, DNS, TLS, and shipping working environments instead of diagrams.
Structured prep tools, decision support, automation, and practical interfaces that help people think and act faster.
These are not just brand names. Each one demonstrates a different mix of product taste, engineering execution, debugging discipline, and follow-through.
Commerce ops across iOS, backend services, and production infrastructure.
BobaHub is a live full-stack product stack spanning customer and store iOS apps, admin tooling, backend APIs, printing flows, notifications, and production deployment. Recent work included standing up a single-VPS production bundle, wiring domains and TLS, and continuing store-side operational features.
Fast iteration on gameplay, progression, persistence, and interface polish.
TypingMaster is a game-like typing app built to feel responsive, motivating, and replayable. Recent work focused on redesigning its evaluation ladder, fixing real persistence bugs, hardening startup/canvas behavior, and improving post-game summaries so the experience feels intentionally crafted instead of merely functional.
Structured preparation workflows with auth, persistence, and system-design tooling.
This project combines a guided prep calendar with authenticated notes, attachments, and persistent system-design sessions. Recent work separated the backend into its own service, repaired the public stack, and fixed state-loss issues so progress and diagram work survive real use.
A learning game that treats educational UX like product design, not homework.
ClockRacer turns analog clock reading into a real game with progression, pressure, and performance feedback. It shows the kind of product work I like doing: sharp loops, measurable improvement, and enough delight that people want to come back.
A repeatable regional content platform for the strings community.
BayStrings and SoCalStrings are proof that careful curation can scale when the underlying content model is strong. Together they show editorial judgment, repeatable information architecture, and steady operational upkeep — not just a static website launch.
I care about clear product thinking, careful implementation, and the last-mile work that makes software usable under real conditions.
I want the product to solve an actual problem, survive contact with users, and keep getting better after launch.
Strong interfaces come from understanding the system underneath them — and strong systems need product judgment to matter.
A lot of the real value comes from fixing the stubborn bugs, deployment issues, and state problems that block trust.
I prefer visible progress, working releases, and grounded proof over abstract promises.