Built once, native everywhere.
I build on a single TypeScript codebase that compiles to web, iOS, Android, and desktop. The interface, data model, and sync logic are written once, so a fix lands on every platform in the same release.
What I commit to in code
Four decisions I make on every project, before the first screen is drawn.
- Local-first data
- Your content lives on the device first and syncs in the background, so the app keeps working with no connection. I collect the minimum a feature needs to run, and no outside analytics SDKs ship in the binary.
- AI that earns its place
- I reach for machine learning when it removes a step you'd otherwise do by hand: sorting, drafting, surfacing the next action. Models run against your data without selling it onward, and anything the AI does, you can undo.
- Performance you can feel
- Screens render from local state, so a tap responds before the network does. I profile on mid-range phones, budget for cold start and battery, and treat a stuttering scroll as a bug rather than a detail.
- Room to grow without a rewrite
- Services split along the seams that change independently, so a spike in one part of a system doesn't drag the rest down. I favor boring, well-understood tools and reach for serverless only where it lowers what I have to operate.
I'd rather ship one feature that holds up under real use than five that demo well and break the first time someone leans on them.
In practice that means fewer toggles and a feature list that grows slowly. Most of the effort goes somewhere users never look: migrations that don't lose data, errors that say what actually went wrong, and updates you don't have to relearn.
What's in the stack
- React & React Native
- TypeScript
- Remix & Next.js
- Tailwind CSS
- Node.js & Python
- PostgreSQL & MongoDB
- AWS Lambda & serverless
- GraphQL & REST
Tell me what you're building.
If you're weighing how to ship across platforms without standing up a whole team, I'm glad to talk through the tradeoffs with you.