Skip to main content
NAKO
United Kingdom · mobile apps

Mobile app developers

From idea to store, for companies that need an app without building a department to make one.

What gets decided at the start

Most projects do not need two native apps. What decides it is real usage: if the camera, notifications or offline work matter, native earns its cost; otherwise a single codebase covers both systems for a different price. Two things are settled at the beginning rather than the end. Data first: a privacy notice inside the app and on the store listing, tracking only after consent, and the ICO as the authority. Then the Children's Code — the ICO's Age Appropriate Design Code applies to services likely to be accessed by under-18s, which is a wider net than services aimed at children. It changes defaults, not decoration: profiling off by default, minimal data collection, no nudging towards weaker privacy settings. Retrofitted, it costs several times what it costs designed in.

What we plan for

Native or shared

Camera, notifications or offline use push towards native; otherwise one codebase covers both systems

Data

Privacy notice in the app and on the listing, tracking after consent, the ICO as the authority

Children's Code

The ICO code applies to services likely to be accessed by under-18s — a wider net than services aimed at children

Store listing

Description and screenshots in British English; American copy costs installs before anyone opens the app

Payments

In-app through Apple and Google; outside the app, card, PayPal and bank transfer

Handover

Source code and store accounts in your company's name, whether or not we continue

What it includes

Development

An app for iOS and Android, plus the site that introduces it.

Marketing

Store visibility and campaigns for the first installs.

Automation

Connections to CRM, stock or booking systems.

Analytics

Usage and drop-off measured without breaching consent.

Audit

Review of existing apps: privacy, performance, accessibility.

How we work

  • We say when a native app is not needed, even though it is the larger job
  • Source code and store accounts yours from day one
  • Children's Code defaults designed in, not bolted on afterwards
  • Fixed stages with sign-off — you do not pay blind to the end
  • Maintenance optional and cancellable monthly

Frequently asked questions

Do we really need two native apps?

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.

Does the Children's Code apply to us?

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.

Who owns the source code?

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.

How long does it take?

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.

Discuss an app

Describe briefly what the app should do — we reply with a view on scope, timing and what the rules require.