App Development
Apps that survive the real world.
An app is judged on the day the signal drops. We build for the awkward states first — offline, slow, half-signed-in, low battery — because those are the ones that cost you a review. Then we get it through review, into the stores, and onto a release cadence you can rely on.
What You Get
The parts that decide whether it works.
One Codebase, Two Stores
iOS and Android from a single build, so a change ships to both without doing the work twice.
Offline First
Local storage and sync designed in from the start, so the app still works on a lift or a farm road.
Native Feel
Platform gestures, keyboards and navigation, so it feels like a phone app rather than a website in a frame.
Store Submission
Listings, screenshots, privacy declarations and review responses handled by us, both stores.
Watched After Launch
Crash and error reporting from day one, so a bad release is found by us rather than reported by a user.
A Release Cadence
Regular, boring releases on an agreed rhythm — the way apps stay stable and keep their ratings.
What lands in your hands
iOS and Android apps that behave properly on a bad connection, ship to both stores, and keep shipping after launch.
Everything below is part of the packages on this page. Anything outside it is quoted before it starts, never after.
Deliverables
- Discovery: flows, screens and data model agreed up front
- Designed screens for every state, including empty and error
- iOS and Android builds from one codebase
- API and backend integration, or a backend built for it
- Offline storage and conflict-safe sync
- TestFlight and Play internal testing for your team
- App Store and Play Store submission and review handling
- Crash reporting, analytics and a post-launch release plan
Pricing
App Development, priced up front.
Pay monthly over twelve months, or once off before we start — the switch shows both.
Launch
R2 450per month × 12 months
R29 400 total over 12 months
A focused first version: the few screens that prove the idea, in both stores, in front of real users.
- Up to 8 core screens, designed and built
- iOS and Android from one codebase
- Accounts, sign-in and push notifications
- Submission to both stores
- Crash reporting and analytics
- 4 weeks of post-launch support
Product
R3 950per month × 12 months
R47 400 total over 12 months
A full product with a backend behind it, offline support and a release rhythm after launch.
- Everything in Launch
- Unlimited screens against an agreed scope
- Backend, admin and API integration
- Offline-first storage and sync
- In-app purchases or payment integration
- Monthly releases for the first 6 months
Platform
Let's talkscoped per project
Multi-phase builds, hardware integrations and apps with a team behind them, priced against a roadmap.
- Everything in Product
- Dedicated discovery and architecture phase
- Third-party, hardware and device integrations
- Ongoing retainer with an agreed release cadence
- Priority support with agreed response times
Prices exclude VAT and third-party costs such as domains, licensing and developer accounts. Hosting is billed separately.
Questions
Before you commit.
iOS and Android, or one first?
Both, from one codebase — building twice rarely pays for itself at this size. If your audience is clearly on one platform we'll still launch there first and hold the other back a release.
Do you handle the App Store accounts?
The developer accounts stay in your name — you own the app. We set them up with you, then do the submissions, the review replies and the store listings from there.
How long until it's in a store?
A first version is usually eight to twelve weeks, plus review time — a day or two on Play, and anything from a day to a week on the App Store for a first submission.
What happens after launch?
Apps need maintenance whether or not they change: OS releases, store policy updates and library security fixes. That's what the post-launch window and the retainer are for.
Ready to bring your idea to life?
Let's create something amazing together.
Firm quote against a scoped roadmap before any work begins.