Mobile apps
Mobile applications (React Native)
Native-feeling iOS and Android apps from one TypeScript codebase — with the same quality gates as the other fields of my development work: clear modules, typed contracts, and criteria-driven verification.
Stack
- React Native + Expo for store builds and a predictable developer loop
- Tamagui for cross-platform UI primitives (shared look & feel with web where it helps)
- TypeScript, React Navigation (native stack / tabs), Safe Area and SVG where needed
- Typed API clients and shared contracts so mobile stays aligned with backend services
- Vitest / typecheck in CI — ship when acceptance criteria pass, not when “it looks fine on my phone”
Native first — web comes with it
With Tamagui on React Native, building a native app for iOS and Android is not a dead-end for the browser: you get a web surface from the same UI primitives instead of maintaining two forever-divergent frontends. That is a huge winner for niche projects that need a careful technical application stood up quickly — often in hours when the stack is already ready — and still want store-grade mobile plus a usable web admin or companion without a second rewrite.
The most important choice for that class of work is not “which framework is fashionable,” but choosing the right stack: forkable licences, typed shared logic, and humans who keep the judgment. One illustrative option (not an endorsement) is named on the niche projects page — use it as a reference for the criteria, then pick what your maintainers can actually own.
How I work
Design-pattern oriented UI shells, vertical features as modules, and careful separation between navigation, presentation and data. Offline-friendly pieces (secure storage, localisation) when the product needs them. AI-assisted delivery under review — same discipline as my other development work.