( Mobile apps )

Apps for iOS and Android, one codebase.

Cross platform apps, plus the backend and admin tooling that has to exist behind them.

An app is rarely just an app. Behind the screens people tap there is an API, a database, an admin panel somebody uses to manage content, push notifications, and an account system. Quotes that cover only the screens tend to grow later.

We build the whole thing, and we build it cross platform, so iOS and Android come from one codebase rather than two teams solving the same problem twice.

( What this covers )

Mobile App Development, in practice

Cross platform builds

One codebase producing both iOS and Android apps. Roughly half the build cost of writing each natively, and one place to fix a bug.

The backend behind it

APIs, database, authentication and file storage, designed alongside the app rather than bolted on once the screens are done.

Admin tooling

A web dashboard for your team to manage content, users and orders, so changing something in the app does not require a developer.

Push notifications

Set up properly, with the permission flows and scheduling that make people keep them switched on.

Payments and subscriptions

In app purchases where the stores require them, Stripe where they do not, and the receipt handling both need.

Store submission

App Store and Play Store listings, review guidelines, privacy declarations and the resubmissions that usually follow a first rejection.

( Worth talking to us if )

Any of this sounds familiar.

Your customers ask for an app and the mobile website is not enough
You need features a browser cannot reach, such as offline use or push notifications
You have a working web product and want a mobile companion to it
You were quoted separately for iOS and Android and want to understand why

( How we work )

The shape of a typical build

01
Decide what version one is
App stores punish abandoned apps. We agree the smallest version worth shipping, then plan what follows it.
02
Design the screens
Mobile design is its own discipline. Screens are agreed in Figma, including the states people hit when something goes wrong.
03
Build app and backend together
Both progress side by side, with builds you can install on a real device as they are made.
04
Submit and support
We handle submission to both stores and the first round of review feedback, which almost always comes.

( What you end up owning )

Everything, and no strings.

The app repository and the backend repository
Figma source files
Signing keys and store listing access, transferred to your accounts
The database and its documentation
Build and release instructions any competent developer can follow

( Built with )

React Native
Expo
TypeScript
Node.js
PostgreSQL
Firebase
Stripe

Mainstream tools with deep talent pools, chosen so you are never dependent on us to maintain what we built.

Questions about mobile apps

Cross platform or native?: Cross platform suits most products, and it is what we recommend by default: one codebase, one set of fixes, roughly half the cost. Native earns its price when an app leans hard on device hardware, heavy graphics or platform specific features. We will tell you which one your product actually needs rather than defaulting to the more expensive answer.
Do the app stores charge separately?: Yes. Apple charges an annual developer fee and Google a one time registration fee. Both are paid on your own accounts, so the app is registered to your business rather than to us.
How long does store approval take?: Usually a few days per store, though a first submission is often rejected over something small in the guidelines. We build that round trip into the timeline rather than treating it as a surprise.
Can the app work offline?: Depending on what it does, yes. Offline support changes how the data layer is designed, so it is worth raising in the brief rather than after the build has started.

Tell us what you need building.

Send a brief and you get a written scope, a timeline and a fixed price back within 48 hours. It costs nothing and commits you to nothing.

Get a quote

( Often paired with )

Mobile App Development, in practice

Cross platform builds

One codebase producing both iOS and Android apps. Roughly half the build cost of writing each natively, and one place to fix a bug.

The backend behind it

APIs, database, authentication and file storage, designed alongside the app rather than bolted on once the screens are done.

Admin tooling

A web dashboard for your team to manage content, users and orders, so changing something in the app does not require a developer.

Push notifications

Set up properly, with the permission flows and scheduling that make people keep them switched on.

Payments and subscriptions

In app purchases where the stores require them, Stripe where they do not, and the receipt handling both need.

Store submission

App Store and Play Store listings, review guidelines, privacy declarations and the resubmissions that usually follow a first rejection.

The shape of a typical build

Decide what version one is

App stores punish abandoned apps. We agree the smallest version worth shipping, then plan what follows it.

Design the screens

Mobile design is its own discipline. Screens are agreed in Figma, including the states people hit when something goes wrong.

Build app and backend together

Both progress side by side, with builds you can install on a real device as they are made.

Submit and support

We handle submission to both stores and the first round of review feedback, which almost always comes.

Questions about mobile apps

Cross platform or native?

Cross platform suits most products, and it is what we recommend by default: one codebase, one set of fixes, roughly half the cost. Native earns its price when an app leans hard on device hardware, heavy graphics or platform specific features. We will tell you which one your product actually needs rather than defaulting to the more expensive answer.

Do the app stores charge separately?

Yes. Apple charges an annual developer fee and Google a one time registration fee. Both are paid on your own accounts, so the app is registered to your business rather than to us.

How long does store approval take?

Usually a few days per store, though a first submission is often rejected over something small in the guidelines. We build that round trip into the timeline rather than treating it as a surprise.

Can the app work offline?

Depending on what it does, yes. Offline support changes how the data layer is designed, so it is worth raising in the brief rather than after the build has started.