Build & Design
Mobile and app development
What this category covers
Mobile and app development is software that lives inside the phone rather than inside a browser. That distinction sounds technical and is almost entirely commercial. An app can send a notification when it is closed, which is the single most common reason a business pays for one. It can reach the camera, GPS, contacts, biometrics and offline storage, so work can continue where there is no signal and sync when there is. And it occupies a place on the home screen, where a link shared in a chat thread disappears within a day.
The work in this category runs from a first build through to the years afterwards. Cross-platform apps, where a single codebase ships to both stores, are what most small and mid-sized businesses should be buying. Native iOS and native Android builds exist for the cases where deep platform capability, regulated data or a single-platform audience make them the right call. Startup MVPs compress the core of a product into weeks so a founder has something real to show. App Store Optimisation deals with the problem that follows launch — a finished app nobody can find. Maintenance keeps a live app compliant as the platforms change beneath it. And watch and television companions extend a product onto screens that need to be designed from scratch rather than scaled.
Two things run through all of it. Almost every app has a backend behind it, so the server side is part of the conversation from the beginning. And publishing is a separate discipline from building — store accounts, compliance forms, testing tracks, review and rejection. That second half is where most projects lose their timelines, so it is scoped, priced and scheduled here rather than assumed.
- Services
- 10
- Detailed pages
- 10
03
Mobile & App Development
10 services
-
01
Native iOS app
A Swift app, taken through to App Store submission.
-
02
Native Android app
A Kotlin app, taken through to Play Store release.
-
03
Cross-platform app
Flutter or React Native — one codebase, both platforms.
-
04
Startup MVP build
The core feature set in eight to twelve weeks, ready for investors.
-
05
App Store Optimisation (ASO)
Title, keywords, screenshots and a ratings strategy.
-
06
App maintenance & releases
OS updates, crash fixes and store compliance.
-
07
Wearable / TV app
watchOS, Wear OS, Apple TV and Android TV companions.
-
08
Mobile game development
A casual or hyper-casual game with monetisation built in.
-
09
App UI/UX redesign
An older app given modern flows and a real visual system.
-
10
Push & engagement setup
Notifications, deep links, in-app messaging and retention loops.
How the work runs.
-
01
Scope
What you actually need from Mobile & App Development, written as deliverables rather than adjectives.
A day or two
-
02
Price and date
A fixed scope, a number and a delivery date, agreed before anyone starts.
Same week
-
03
Build
The work itself, with something you can open and look at rather than a status report.
The bulk of it
-
04
Handover
Files, access and a walkthrough. Nothing is held hostage.
Final day
See where the site stands before you brief anyone.
Before scoping Mobile & App Development work, it helps to know what the site is doing today. The audit reports what it checked, what it found, and — the part most tools leave out — what it could not check, and why.
Questions people ask before they commit.
- Do I need an app, or would a mobile website do the job?
- A fair question and the first one we ask. If people will open the thing once a month, a good mobile site is faster, cheaper and needs nobody's permission to publish. An app earns its cost when you need to reach into someone's pocket with a notification, when you need the camera, GPS, offline storage or biometrics, or when being on the home screen is itself the point.
- Who owns the App Store and Play Console accounts?
- You do, always. The listing names a seller and that should be your business, the reviews and install history are yours, and if the relationship ends you keep everything. We take member access, which is enough to publish on your behalf. Apple's own rules point the same way.
- How long until it is actually live?
- Split the answer in two, because the second half is not ours. A build has a date we can commit to. After submission, Apple and Google decide, and a first rejection is common rather than alarming. We quote the build and then state the review window separately, so a delay at that stage is expected instead of surprising.
- Native or cross-platform?
- Cross-platform for most business apps, because one codebase means one set of features arriving on both stores on the same day and one maintenance bill instead of two. Native where you need deep hardware access, sustained performance, or platform features that appear first on one side. Watch and television companions are always native, because cross-platform tooling does not reach them.
- What does an app cost to keep running once it is built?
- Something, every year, whatever you do. iOS ships annually and Apple periodically requires builds against a current SDK. Google raises the target API level and blocks updates from apps that fall behind. Certificates and developer memberships expire. That is why maintenance is offered as a defined monthly service rather than left to become an emergency.
- Can you work on an app someone else built?
- Yes, starting with a short paid review of the code, the build setup, the signing keys and the state of both store accounts. An app left untouched for a year is a different quotation from one handed over cleanly last quarter, and quoting before looking would be guessing at your expense.