06

Mobile App Development

iOS and Android apps built cross-platform where that fits and natively where it does not — including the release process nobody warns you about.

01 / OVERVIEW

What this is.

An app is a heavier commitment than a website. It has to be submitted, reviewed, updated and supported across two stores with their own rules, and a rejected build can cost a fortnight. We are straightforward about that before you commit.

We also ask the awkward question first: does this need to be an app? A responsive web build is cheaper, faster and easier to change. Where the answer is genuinely yes — offline use, device features, push, a repeated daily task — we build it properly.

02 / WHAT IS INCLUDED

The scope.

Platform decision

An honest recommendation on cross-platform versus native, and on whether an app is warranted at all.

App build

iOS and Android, with a shared codebase where that is the right call.

Backend and API

The services the app depends on, built alongside rather than assumed.

Store submission

Listings, assets, review requirements and the resubmissions that follow.

Release process

Versioning, staged rollout and a way to ship a fix quickly.

Post-launch support

Because an app that is never updated stops working when the OS moves.

03 / HOW IT RUNS

Four phases.

01

Validate

Whether an app is the right shape for the problem, and what it must do on day one.

02

Discovery

Screens, data model, platform decision and a costed plan.

03

Build

Phased, with builds you can install and try rather than only see in screenshots.

04

Ship

Store submission, release and the support arrangement that follows.

04 / WHAT YOU END UP WITH

The outcome.

  • A clear answer on whether you need an app at all
  • Apps live on both stores with the listings done properly
  • A release process you can run without us
  • A support arrangement that keeps it working as the platforms change
05 / QUESTIONS

Before you ask.

Cross-platform or native?

Cross-platform for most business apps — one codebase, lower cost, faster changes. Native where performance, device features or platform conventions genuinely demand it.

Do you handle the App Store accounts?

You should own the developer accounts, and we will help you set them up. Handing your store presence to an agency is a risk we would not accept ourselves.

How long does review take?

Usually days rather than weeks, but rejections happen and the first submission is the slowest. We build that into the plan rather than promising around it.

Starting investments are on the pricing page. The figure for your project comes from a written proposal you see before anything begins.

MORE / SERVICES

Other disciplines.

All eight disciplines

Is this the right fit?

Describe the problem and we will tell you honestly which discipline it belongs to.

Talk it through