From idea to store, for companies that need an app without building a department to make one.
Camera, notifications or offline use push towards native; otherwise one codebase covers both systems
Privacy notice in the app and on the listing, tracking after consent, the ICO as the authority
The ICO code applies to services likely to be accessed by under-18s — a wider net than services aimed at children
Description and screenshots in British English; American copy costs installs before anyone opens the app
In-app through Apple and Google; outside the app, card, PayPal and bank transfer
Source code and store accounts in your company's name, whether or not we continue
An app for iOS and Android, plus the site that introduces it.
Store visibility and campaigns for the first installs.
Connections to CRM, stock or booking systems.
Usage and drop-off measured without breaching consent.
Review of existing apps: privacy, performance, accessibility.
Often not. If the camera, notifications or offline use are not involved, a single codebase covers both systems at a different cost. We decide it on the use case rather than on what is fashionable.
It applies to services likely to be accessed by under-18s, which is broader than services aimed at them. If your app has no age gate and a general audience, it probably does. We check before design rather than after, because the code changes defaults, not decoration.
You do, from day one. The code sits in your repository and the store accounts are in your company's name. Changing supplier should be a decision, not a hostage situation.
A first usable version is usually three to four months depending on scope. We work in stages with sign-off, so you see something after each step and can change direction while it is still inexpensive.
Describe briefly what the app should do — we reply with a view on scope, timing and what the rules require.