Services
Mobile app development
Native and cross platform apps for iOS and Android. We publish our own app on the App Store, so we know what shipping actually costs.
We ship our own app, not just client work
Apex Health: Sleep & Recovery is our own iOS and watchOS product, built with SwiftUI and HealthKit and published under our own developer account. Store review, privacy manifests, entitlements, background execution limits and watch complications are problems we solve on our own time as well as yours.
Swift and SwiftUI
Built against the current platform rather than a wrapper: widgets, Live Activities, Siri shortcuts, watch apps and the privacy manifest the App Store now requires.
Kotlin and Jetpack Compose
Modern Android with a single source of truth for state, work scheduling that respects battery limits, and a release path through the Play Console.
When one codebase is the right call
React Native or Flutter when the product is mostly shared logic and the schedule matters more than platform polish. We will say plainly when native is the better answer.
Through review, not up to it
Store listings, screenshots, age ratings, privacy questionnaires, phased rollout and crash monitoring. An app that cannot pass review is not finished.
What we build with
Platform choice is a business decision, not a taste one. We make the recommendation in discovery and write down the reasoning.
How the work runs
Agree the problem
A short paid discovery. We read the existing system, talk to the people who use it, and write down the scope, the risks and what success means before anyone opens an editor.
Decide before building
Flows, screens and the data model, reviewed with you. Deciding on a prototype costs hours. Deciding in production costs weeks.
Ship in slices
Two week iterations, a working build at the end of each, and a demo you can click. You see progress as software, not as a status report.
Stay after launch
Monitoring, fixes and small improvements under a support retainer, or a clean handover to your own team with the documentation to run it.
Questions we get asked
Native or cross platform?
It depends on how much of the product is platform specific. Heavy use of sensors, background work or system integration favours native. A largely shared interface over a shared API favours cross platform. We recommend one and explain why.
Do you handle App Store and Play Store submission?
Yes, including the listing, screenshots, age rating, privacy questionnaire and phased rollout. We can publish under your developer account or guide your team through setting one up.
Can you take over an app someone else built?
Often, yes. We start with a review of the code, the dependency versions and the release setup, then give you an honest read on whether to continue it or rebuild the parts that are holding it back.
What about privacy rules?
Store privacy questionnaires and privacy manifests are part of delivery, not an afterthought. Our own app processes health data entirely on the device, and we bring the same default to client work.
Do you build for tablets and wearables?
Yes. Apple Watch, iPad and Android tablet layouts are scoped explicitly rather than assumed, because each one is real work.
Planning an app, or stuck with one?
Send us the idea or the repository. We will come back with a scope, a platform recommendation and a range you can plan against.