Mobile app development services for iOS and Android
We build iOS and Android apps from one React Native codebase, with Expo, on the same TypeScript backend as your web product. You get both stores, one set of business rules, and accounts that belong to you.
A written scope and a fixed budget before any work is billed.
One codebase, both stores, one backend
Most business apps do not need two separate native codebases. React Native renders real iOS and Android controls from one TypeScript codebase, and Expo handles the builds, store submissions and over-the-air updates. It is the stack we use for our own apps, which is why we recommend it.
The bigger saving is on the server. If you already run a web product, the app can use the same API, the same accounts and the same business rules, so a pricing change is made once and both platforms follow it. If you do not have a backend yet, we build one that the web and the app share from the start.
We usually suggest proving the core workflow on the web first, where changes ship in minutes, and moving to mobile once people use it. When the app is the product itself, we start there. The UI/UX design work for either comes first, as a prototype you can tap through on a phone.
Sound familiar?
Two app quotes, two codebases, twice the bugs
Separate iOS and Android teams mean every feature is built twice and the two apps drift apart a little more with each release.
The app and the website disagree
Prices, stock or account status differ between the web and the app because each has its own logic and its own copy of the data.
The previous agency owns the store account
Your app is published under someone else’s developer account, and moving it means asking a vendor who has stopped replying.
Every fix waits for store review
A typo in a screen takes days to reach users because each change goes through a full store submission.
What a mobile build covers
Everything between the idea and an app your customers update without thinking about it.
iOS and Android apps
One React Native codebase with native controls, push notifications, offline handling and device features such as the camera and location.
- React Native
- Expo
- Push
Shared backend and API
The same accounts, data and business rules as your web product, so the two never disagree.
- API
- Auth
- Sync
Store release and updates
Builds, App Store and Google Play submission under your accounts, and over-the-air updates for fixes that do not need a full review.
- App Store
- Google Play
- OTA
What you keep at the end
Everything below is yours from the first commit, under your own accounts wherever possible. Nothing in it is licensed from us, and nothing can only be maintained by us.
your-company/
- docs/requirements.mdThe written scope and the fixed budget for the first release.
- app/The React Native and Expo codebase for both platforms.
- api/The backend the app and your web product share.
- store/Store listings, signing and builds under your developer accounts.
- docs/runbook.mdHow to build, release, push an update and roll one back.
Four stages, and what
each one hands you
Every stage ends in something you can review and keep, including the stages that come before any code is written.
Discovery and requirements analysis
We map the real problem before any code is written: stakeholders, constraints, existing systems, and what success means in measurable terms.
- requirements.md
- scope + fixed budget
- risk register
Design and architecture
Interface flows and system architecture designed together, so what we specify is what we can build and scale.
- clickable prototype
- system diagram
- data model
Build, with a weekly demo
Short delivery cycles with visible progress. You review working software throughout, not a finished system revealed on launch day.
- staging deploy / cycle
- test suite + CI
- weekly demo
Launch, then operations
We deploy the system, monitor it, and hand over the runbook. We then continue to operate it under a monthly agreement you can end with 30 days’ notice.
- production infra
- runbook + handover docs
- monitoring + alerts
Terms we put in writing
before work begins
The figures we commit to on every engagement. Your project gets its own dated plan on top of them.
- Inquiry
- 1 business dayA reply from someone who has read the brief.
- Discovery
- 1 to 3 weeksEnds in a written scope and a fixed budget.
- Weekly review
- Every weekThe work as it stands, on a link you can open yourself.
- First release
- 8 to 16 weeksTypical time from the end of discovery to production.
- Operations
- 30 days’ noticeMonitoring and iteration under a monthly agreement.
Illustrative. Every project receives its own dated plan before work begins.
What decides the cost of an app
Building for both platforms from one codebase removes the largest cost multiplier in mobile work, which is doing everything twice. What remains depends on the app itself, and the price for it is fixed once discovery has written the scope.
- 01Whether a backend already exists, or has to be built with the app
- 02Offline use, background sync and push notifications
- 03Device features: camera, location, payments, biometrics
- 04How many user roles and screens the first release needs
- 05Integrations with your existing systems
- 06Store release and ongoing updates after launch
What we build it with
Tools with long support horizons and large talent pools, so the system stays maintainable by any capable team, not only ours.
React Native
Native iOS and Android interfaces from one codebase, by the largest community in cross-platform mobile.
Expo
Builds, store submissions and over-the-air updates without maintaining two native toolchains.
TypeScript
The same types in the app and the backend, so an API change that would break the app fails the build.
Node.js
The API the app and your web product both talk to.
Questions buyers ask us
The ones that come up most in first conversations about this service.
Something not covered here?
Email us at hello@kodfabrika.com.
Related services
Built to last.
Started this week.
Tell us what you’re building. You’ll receive a written scope, a defined budget, and a delivery plan. Not a proposal deck.