iOS and Android apps from one codebase.
I design and build mobile apps for iOS and Android from a shared codebase — giving you one product to build, maintain, and evolve across both platforms. Auth, shared APIs, push notifications, and App Store and Google Play deployment are part of the build.
Scope
What I build
iOS & Android apps
React Native apps
Companion apps for a web product
Store-ready production apps
Auth & user accounts
Push notifications & realtime
Approach
From the first screen to the store.
I don't wrap a website and call it an app. It has to feel right on a phone — the flows, the interface, the APIs behind it, and a production build that can actually ship to the stores.
Product & UX
Design the experience for a phone — navigation, gestures, and the jobs people open the app to do. Not a desktop layout squeezed down.
Mobile app
Build the iOS and Android app from one codebase, with the screens, state, and native pieces the product actually needs.
Backend & APIs
Shared APIs with your web product, or a backend built for the app: auth, accounts, data, and push.
Store & production
Signing, builds, TestFlight, Play Console, store listing, and the release process so the app can actually go live.
Capabilities
What I can handle
Mobile app
- React Native
- Expo
- TypeScript
- Navigation
- Native UI
- Design implementation
Platforms & delivery
- iOS
- Android
- App Store
- Google Play
- TestFlight
- OTA updates
Product systems
- Authentication
- User accounts
- Push notifications
- Realtime
- Deep links
- Device APIs
Integrations
- Shared web APIs
- Payments
- Analytics
- Maps & location
- Notifications
- Third-party SDKs
Production
- CI/CD
- Store deployment
- Signing & builds
- Monitoring
- Versioning
- Release process
Difference
What goes into the build
One codebase, two stores
iOS and Android from the same app, so you're not running two teams and two roadmaps for the same product.
Shared with your web product
The app can sit on the same APIs, auth, and data as the website or SaaS — not a separate product that drifts out of sync.
Built for the phone
Navigation, performance, gestures, device capabilities, and platform-specific behavior are part of the build — not an afterthought once the web version is finished.
End-to-end ownership
You work directly with the person designing, building, and shipping the app — including the store release.
Process
How a project works
- 01
Understand
We figure out what the app is for, who it's for, and whether it needs to share a backend with something you already have.
- 02
Design
I turn that into the structure, flows, and interface for a phone.
- 03
Build
The app, APIs, auth, notifications, and the systems behind it.
- 04
Ship
Store builds, a production pass, and an app that's actually ready to submit.
FAQs
Do you build for both iOS and Android?
Yes. One React Native codebase ships to both stores. Platform-specific behavior gets handled where the product actually needs it.
Can you build an app for an existing website or SaaS?
Yes. The app can use your existing APIs, authentication, database, and product infrastructure rather than becoming a completely separate system.
Can you handle the backend too?
Yes. I can build or extend the APIs, authentication, data layer, notifications, and other backend systems the app needs.
Can you integrate payments and subscriptions?
Yes. Payments and third-party services can be integrated depending on the product and the platform requirements.
Do you handle App Store and Google Play submission?
Yes. Production builds, signing, TestFlight, Play Console, store configuration, and the release process. I don't hand you an IPA and leave.
Can you add push notifications, maps, or realtime features?
Yes. Those get built into the app when they're part of the product experience.