One codebase, three platforms.
Expo and React Native for iOS and Android, Next.js for the web app and admin, one backend and one data model under all of it. A feature is built once and lands everywhere.
Mobile app development
iOS and Android from one codebase, at a fixed price.
Expo and React Native apps with the web app and admin behind them, submitted to both stores, in four to eight weeks. $10K–$25K, agreed in writing before work starts.
- $10K–$25K
- Fixed, in writing
- 2 stores
- iOS + Android
- 1
- Codebase, web included
- 4–8 wks
- Scope to stores
How it is built
Four decisions that keep a mobile build on a date.
Store builds through EAS from week one.
The first TestFlight and Play internal build goes out in the first week, so store accounts, certificates and review surprises are dealt with early, not the night before launch.
Subscriptions through RevenueCat.
In-app purchases on both stores, receipts validated, entitlements shared with the web app, so a subscriber on the phone is a subscriber on the laptop.
Shipped apps to point at.
Month6 is on the App Store. RapidCharge is on the App Store and Google Play and generating revenue. Resumemaster runs web and mobile from one codebase. Every one is on the projects page.
What a Product Build includes
The whole product, not just the app.
Where a build lands in the $10K–$25K band depends on platforms, flows and integrations. The scoping call settles all three and the number does not move unless the scope does.
iOS and Android apps
Native apps from the same codebase with Expo, with push notifications, deep links and offline-tolerant screens where the product needs them.
The web app and admin
The same product on the web, plus the admin you run it from: users, content, payments, whatever the operation needs to see.
Payments in the stores and on the web
RevenueCat for in-app purchases, Stripe on the web, one entitlement model across both.
AI features where they earn their place
Chat, search over your data, extraction, generation, with the model chosen per problem and kept swappable. Not added for the label.
Store submission
Listings, screenshots, builds and review feedback handled until both apps are live. Developer accounts stay in your name.
Source, runbook, 30 days of support
Everything in your GitHub, your cloud and your store accounts from the first commit. A month of fixes after launch.
How it runs
Four steps from scope to stores.
Scope
Platforms, flows and integrations agreed on a 30-minute call and written into a one-page scope with a fixed price and a launch date. 50% invoiced on signing.
Skeleton
Week 1: the web skeleton deployed, the shared backend and data model in place, the first TestFlight and Play internal build out through EAS.
Build
Weeks 2–6: flows land one at a time across web and mobile, with a live demo every three to four days and daily progress in Slack.
Stores
Production deploy, store submissions, monitoring, handover. The second 50% on deployment. If the date agreed at scoping is missed, the second half is waived. App Store and Google Play review time does not count against the date. The date moves only if the scope changes in writing.
Questions
What people ask before they book.
- How much does it cost to build a mobile app?
- $10K–$25K here, fixed in writing after a scoping call, and that includes the web app and admin behind it. Web plus one mobile platform with a few flows sits near the bottom of the band; web plus iOS plus Android with an admin, subscriptions and model work sits near the top.
- How long does it take to build a mobile app?
- Four to eight weeks from a signed scope to both stores. There is a web skeleton and a first test build in week one, a demo every three to four days after that, and the launch date is in the contract.
- React Native or native Swift and Kotlin?
- Expo and React Native, because one codebase reaching iOS, Android and the web is what makes a fixed price and a four-to-eight-week date possible. It is the same stack behind Month6 and RapidCharge. If a product needs something only native code can do, that part is written natively and called from the shared app.
- Do I need the web app too?
- Almost always, and it comes with the build. Users sign up and pay more readily on the web, support and admin live there, and the stores take a cut of anything sold inside the app. The web app is also where the product is demoed to you every few days.
- Do you handle the App Store and Google Play?
- Yes. Developer accounts are created in your name, and listings, screenshots, builds and review feedback are handled by Codeks until both apps are live.
- What about the date if store review is slow?
- If the date agreed at scoping is missed, the second half is waived. App Store and Google Play review time does not count against the date. The date moves only if the scope changes in writing. In practice the first build goes to the stores in week one, so review problems surface early.
- Which mobile apps have you shipped?
- Month6, a fitness app on the App Store with a six-month projection and an AI coach. RapidCharge, an EV charging app on the App Store and Google Play that is generating revenue. Resumemaster, web and mobile from one codebase. Codeks Charge, a white-label platform with branded driver apps. All of them are on the projects page with a link to the live product.
Start here