iOS & mobile apps
Native iOS where the platform matters, React Native where one codebase is the point.
How I approach it
The choice between native and cross-platform is usually decided by one requirement rather than by preference. If an app leans on the camera, the Neural Engine, or 3D rendering, native Swift stops being an argument. If the product is mostly screens and data, React Native gets both platforms for one codebase and one maintenance burden.
I do both, and I have shipped the awkward case: a React Native app with a native Swift capture module underneath it, because the measurement had to run on Apple's Vision framework while the rest of the product stayed cross-platform.
On-device work is a recurring theme — pose estimation for a clinical measurement, OCR that reads a label without uploading it, power-efficient models on a ring with a battery measured in days. Keeping inference on the device is often a privacy position as much as a performance one.
What this covers
- Native iOS in SwiftUI, including camera, Vision, and SceneKit work
- On-device inference where the cloud is too slow, too costly, or not permitted
- StoreKit 2 subscriptions and paywalls
- React Native and Expo for teams that need iOS and Android from one codebase
What you get
- An app that builds and runs on real hardware, not just the simulator
- Test coverage on the logic that matters, separated from the UI
- App Store submission handled, or documented if you would rather do it
- A written note on why native or cross-platform was the right call here
Relevant work
Other services
Need this on a project?
Describe what you are building and where it is stuck. The scoping call costs nothing, and you get a written scope and price before any work starts.