Mobile apps

Mobile app development for iOS and Android, scoped to what users will actually use

An app is worth building when people will open it again and again. We help you decide whether yours is one, then design, build and publish it for iOS and Android from one codebase.

Why this option

When it's the right call.

A lot of apps get built because a business feels it should have one, then sit unused on a few hundred phones. The ones that work do a job people repeat: reordering, booking, tracking a delivery, logging work in the field, checking a balance. Before anything is designed, we test your idea against that question. If an app is the right answer, we build it cross-platform, so iOS and Android share one codebase and one budget, and we keep the first version focused on the job people will come back for.

  • Your customers repeat an action often enough to want it on their home screen
  • Staff in the field need a tool that works on their phone, sometimes offline
  • You need features a website cannot do well: notifications, camera, location
Who it's for

A good fit if…

  • Businesses with repeat customers: ordering, booking, loyalty, subscriptions
  • Companies with field teams who need to log jobs, photos or signatures on site
  • Startups whose product is mobile-first by nature
  • Businesses with a working web application that now needs a native app
Probably not, if

Maybe look elsewhere if…

  • People would only use it once or twice. A fast mobile website does that job for far less
  • You need it to win search traffic. Apps do not rank in Google, your website does
  • The budget only covers launch, with nothing for updates. Apps need maintenance as phones update
What you get

What's included.

  • A short discovery to test the idea and define the first version
  • UX design and a clickable prototype you can try on your own phone
  • Cross-platform development for iOS and Android from one codebase
  • A backend and admin panel, or integration with your existing system
  • Push notifications, payments, maps, camera or offline mode where the app needs them
  • Testing on real devices across screen sizes and OS versions
  • App Store and Google Play submission, under your own developer accounts
  • Analytics and crash reporting from day one
Under the hood

How we actually build it.

The detail that separates a page that ranks and converts from one that just exists.

Cross-platform, and why it is usually the right call

Building separate native apps for iOS and Android means two codebases, two sets of bugs and roughly twice the cost. For most business apps, a cross-platform framework such as React Native produces apps that look and feel native on both, from one codebase. It also shares skills and sometimes code with a React or Next.js website.

There are exceptions: heavy 3D, unusual hardware access or very demanding performance. If your app is one of them, discovery will say so and the quote will reflect it.

The first version should do one job very well

The most expensive mistake in app development is building everything at once. We define the one journey users will repeat, such as reorder, book or log a job, and make that fast and reliable first. Everything else waits for evidence that people want it.

That keeps the first release smaller, cheaper and quicker to market. It also means the next decisions are made on real usage data rather than guesses.

Backend, admin panel and the systems behind it

An app is only the front of a system. Behind it sits the data, the business logic and an admin panel your team uses to manage orders, users or content. We build that backend, usually in Laravel, or connect the app to the system you already run, whether that is custom software, an e-commerce store or a CRM.

Publishing, updates and the work after launch

We prepare the store listings, screenshots and privacy details Apple and Google require, and submit the app under developer accounts in your name. Store review can take from a day to a couple of weeks, and the plan allows for it.

After launch, phones and operating systems keep changing, and an app that is not maintained starts to break. An ongoing plan covers OS updates, fixes and new features, and crash reporting tells us about problems before your reviews do.

Switching over

Migrating from something else?

A mobile website customers keep asking to "make an app" An old app with poor reviews Separate iOS and Android apps that are expensive to maintain

If you already have an app that users dislike, we start by reading the reviews and the crash reports. They usually point to the same few problems. A rebuild keeps the same store listings, so existing users get an update rather than having to find a new app, and their data and logins move across. If you are replacing two separate native apps with one cross-platform codebase, we plan the switch so both platforms update together.

Avoid these

Common mistakes we don't make.

  • Building an app for something people would only do once
  • Cramming every feature into version one
  • Publishing under the developer's store account instead of the business's own
  • No analytics, so nobody knows which features are used
  • No budget for updates, so the app breaks a year later with a new OS version
  • Ignoring how anyone will find the app in the first place
Pricing

What it costs.

Fixed and itemised. Remove anything you don't need, add anything you do.

Discovery & prototype

From $1,500

Test the idea before you build it.

  • Discovery and scope
  • UX flows
  • Clickable prototype on your phone
  • Staged build quote
Recommended

First release

Custom quote

A focused app on both stores.

  • Everything in the prototype stage
  • iOS and Android, one codebase
  • Backend and admin panel
  • Store submission
  • Analytics and crash reporting

Full product

Custom quote

Larger apps and integrations.

  • Multiple user types
  • Payments and subscriptions
  • Offline mode
  • Complex integrations

Add-ons

  • Maintenance and OS updatesQuoted
  • App landing pageQuoted
  • Store listing optimisationQuoted
Straight talk

When we'd point you elsewhere.

We'd rather lose the sale than sell you the wrong thing.

Questions

Before you get in touch.

How much does it cost to build an app?

A discovery and clickable prototype starts from $1,500. The build itself is quoted from that prototype, stage by stage, because the cost depends heavily on features such as payments, several user types or offline mode.

Do you build for both iOS and Android?

Yes. We usually build cross-platform, so both apps come from one codebase, which keeps the cost and the maintenance close to a single app.

How long does an app take?

A prototype takes two to four weeks. A focused first release usually takes eight to fourteen weeks after that, plus store review time.

Will the app be published in my name?

Yes. It is published under Apple and Google developer accounts you own, and the code is handed over to you.

Do I need an app or a website?

If customers repeat an action often, or you need notifications, camera or offline use, an app can be worth it. If they visit occasionally or find you through search, a fast website does more. We will tell you which in discovery.

More general questions about working with us are answered on the FAQ page, or just ask us directly.

Thinking about mobile app development?

Send us your site or your idea. We'll tell you honestly whether this is the right approach, what it would take, and roughly what it would cost. No pitch deck, no pressure.