C O D E X L A V A
Skip to content

Mobile App Development for iOS & Android

Mobile apps

One codebase. Both app stores.

Codexlava builds iOS and Android apps for UK businesses from a single React Native codebase — customer apps, field and staff apps, and mobile front doors to the systems you already run.

Every feature is built once, the app shares a back end with your website, and it is published under your own store accounts, so it is yours from the first day.

At a glance

The short answers

More questions
What is React Native?
React Native is an open-source framework, created by Meta, for building iOS and Android apps from one JavaScript or TypeScript codebase. It draws the phone's own native interface components rather than showing a web page inside an app, so the result looks and behaves like any other app on the device.
Should a business app be native or cross-platform?
For most business and customer apps, cross-platform with React Native is the better trade: one codebase instead of two, so every feature and fix is built once. Fully native Swift and Kotlin apps earn their extra cost for graphics-heavy games and deep hardware work. Codexlava builds React Native, and says on the first call if a project needs native instead.
How much does it cost to build a mobile app in the UK?
It depends on the number of screens, whether a back end already exists, and how many systems the app connects to. One React Native codebase avoids paying for the same feature twice. After launch there are running costs: hosting for the back end, Apple's annual developer programme fee, Google's one-off registration fee, and updates as phones change. Codexlava scopes each app individually and the first consultation is free.
Does Codexlava publish apps to the App Store and Google Play?
Yes. Codexlava prepares the listings and privacy details and submits the app to both stores under the client's own developer accounts, so the business owns the app, its listings and its reviews from the first day.
What we build

Apps that do a job, not just sit on a screen

A business app earns its place when people use it again and again. These are the five kinds we are asked for most.

01 / 05

Customer apps

Bookings, accounts, orders and repeat purchases in your customers’ pockets — on the same back end as your website, so a change made in one place shows up in both.

  • Accounts & sign-in
  • Bookings & orders
  • Push notifications
02 / 05

Field & staff apps

Jobs, checklists, photos and signatures captured where the work happens, and synced when there is signal.

  • Offline-ready
  • Camera & forms
03 / 05

Companion apps

A mobile front door to a platform you already run, using its existing data and rules.

  • Your API
  • Shared logic
04 / 05

MVP apps

The smallest app that puts the idea in front of real users, on foundations the full product can grow from.

  • Prototype first
  • Real users
05 / 05

Payments & integrations

Stripe for physical goods and services, plus the CRM and office systems the app needs to talk to.

  • Stripe
  • HubSpot
  • Microsoft 365
Choosing the approach

Native, React Native or a web app?

We build React Native, because for most business apps it is the better trade. This is where each option wins — including the two we would not sell you.

How the three approaches compare
Fully nativeSwift and Kotlin React NativeWhat we build Web appIn the browser
Codebases to maintain Two, one per platform One, for iOS and Android One
In the App Store and Google Play Yes Yes No — opened from a link
Device features All of them, first Nearly all, through native modules A limited set
Cost of a change Made twice Made once Made once
Best for Graphics-heavy games, deep hardware work Most business and customer apps Tools that do not need an app icon
The UK market

Your customers already live on their phones

Most of the time UK adults spend online is now spent on a smartphone, across dozens of apps a month. And since April 2026, Apple and Google have been held to fairer app review commitments by the UK competition regulator.

4h 30m a day spent online by the average UK adult, up 10 minutes in a year
~¾ of that time is on a smartphone
41 different smartphone apps used by the average adult each month
Apr 2026 CMA commitments on fair, transparent app review by Apple and Google took effect

Sources: Ofcom, Online Nation 2025 (December 2025); Competition and Markets Authority, app store commitments (February 2026). Market context, not Codexlava results.

From idea to the stores

Five steps, both platforms at once

The same four-stage process as every build, with the parts only an app has.

  • Design

    Screens you can hold

    User flows, wireframes, then a clickable prototype you try on your own phone — the cheapest point to change your mind.

  • Build

    One codebase, one back end

    React Native and TypeScript for the app; an API in Django, FastAPI or Express.js that your website or other systems can share.

  • Test

    On real devices

    iPhones and Android phones of different sizes and ages, because a simulator does not have a weak signal or an old battery.

  • Publish

    Into both stores

    Listings, screenshots and privacy details prepared and submitted under your own developer accounts, so the app is yours from day one.

  • Run

    Updated as phones change

    Apple and Google release new operating systems every year. Crash reports come in through Sentry, and updates go out through the same stores.

What it is built with

The app is the visible part. The back end does the work.

Same mainstream tools as the rest of our stack, so the app, the website and any internal tools can share one system.

App
  • React Native
  • TypeScript
  • JavaScript

One codebase for iOS and Android, with types to keep a growing app maintainable.

API & back end
  • Django
  • FastAPI
  • Express.js

The server the app talks to — and the same one your website or internal tools can use.

Data & background work
  • PostgreSQL
  • MongoDB
  • Redis
  • Celery

Records, sync and the slow jobs — notifications, imports, reports — run off the request so the app stays quick.

Connects to
  • Stripe
  • HubSpot
  • Microsoft 365

Payments, customer records and staff sign-in, through the systems you already pay for.

Runs on
  • AWS
  • Azure
  • Docker

The back end, containerised and sized for real usage rather than a launch-day guess.

Quality & delivery
  • Sentry
  • Bitbucket Pipelines
  • GitHub

Crash and error reporting from real phones, and every change built and checked before release.

Is this right for you?

Who this is for, and who it is not

If you are in the second column, we will say so on the first call rather than sell you something you do not need.

Good fit

A good fit if…

  • Customers or staff need it on their phone, not at a desk
  • You need iOS and Android without paying for two builds
  • The app shares data with a system you already run, or one we build alongside it
  • You want to own the code and the store listings outright
Probably not

Not the right fit if…

  • It is a graphics-heavy game, or needs deep hardware work where native is the better choice
  • You need it in the stores this month
  • Your project needs a supplier holding Cyber Essentials, NHS DSPT or DCB0129 clinical-safety sign-off — we do not hold those yet
What you receive

What you have at the end

You approve each stage before the next one starts, and you own everything you paid for.

  1. Screen flows and a clickable prototype

    Tried on your own phone and signed off before the build starts.

  2. The back end and API

    Built once, and ready for your website or other systems to share.

  3. Test builds on your devices

    Working app builds throughout, not a demo at the end.

  4. Store listings and submission

    Prepared and submitted to the App Store and Google Play under your accounts.

  5. Documentation and handover

    So your own team, or whoever comes next, can maintain and release it.

FAQ

Questions about mobile apps

Testing an app idea first? Start with an MVP — the smallest version that real users can try.

Do we need an app, or would a website do?
Often a website will do, and we will say so. An app earns its place when people use it repeatedly, need it offline or on the move, or need push notifications, the camera or other phone features. If customers will use it once, a fast mobile website is usually the better spend.
Will Apple or Google take a cut of our sales?
Only for some kinds of sale. Digital content and subscriptions sold inside an app generally go through the store's billing, which charges a commission. Physical goods and real-world services, such as orders, bookings and deliveries, are usually paid through your own payment provider, such as Stripe. The rules and rates have been changing under the UK's Competition and Markets Authority, so we check the current position for your app during scoping.
Can the app work without a signal?
Yes, if it is designed for it from the start. Field and staff apps usually need to capture work offline and sync when the connection comes back, which affects how the data is stored and how conflicts are handled. It is much harder to add later, so we ask about it during discovery.
Can the app share a back end with our website or existing system?
Yes, and it usually should. One API serving the website, the app and any internal tools means one set of rules and one copy of the data. If you already have a system with an API, the app can often use it directly.
Who owns the app and the store listings?
You do. Apps are published under your own Apple and Google developer accounts, and you own the code, the listings and the reviews. Documentation is handed over so your own team, or another developer, can carry on.
Do you build native Swift or Kotlin apps?
No. Codexlava builds with React Native. For most business apps that is the better trade, but for graphics-heavy games or apps that live deep in the hardware, a native specialist is the right call, and we would tell you so rather than stretch.
How do updates work after launch?
Apple and Google release new operating system versions every year, and apps need occasional updates to keep working well on them. Crash reports from real phones arrive through Sentry. Updates are built, tested and submitted through the same stores, and how much of that we handle is agreed before launch.
How long does app store review take, and can an app be rejected?
Review times vary and an app can be rejected, most often for missing privacy information, broken sign-in for the reviewer, or content that breaks a store guideline. We prepare for review as part of the build, and since April 2026 Apple and Google have committed to the CMA to review apps in a fair, objective and transparent way.

Tell us what you are building

One call, no obligation. We will tell you what the work involves, roughly what it costs, and whether we are the right people to do it.