One codebase, both app stores, wired to your back office

Building the same app twice costs roughly twice as much and takes twice as long to change. Unless you need something the shared approach genuinely cannot do, one codebase serving both stores is the better trade, and we will tell you when it is not.

Free first call. Fixed price before you commit. Source code handed over at launch.

The problem

Where app projects overrun

Rarely in the build. Usually in store review, in the offline behaviour nobody specified, and in the slow realisation that the app needs data the back office was never designed to hand out.

  • Store rejection over rules nobody read until submission
  • No plan for what the app does with no signal
  • A back office with no API, discovered halfway through
  • Two separate codebases drifting apart with every release
how we price it
free call ... 30 minutes
written plan ... within 48 hours
price ... fixed, not hourly
sprints ... 2 weeks each
source code ... yours at launch

If the price does not work we cut scope together until it does, before you pay anything.

Detail 01

What we build

Customer apps

Ordering, booking, loyalty and account access, in your brand.

Field staff tools

Job lists, forms, photos and signatures that keep working with no signal and sync later.

Delivery and tracking

Driver apps with routing, and tracking your customer can follow.

Internal tools

The thing your team currently does on paper or a spreadsheet on a phone.

Detail 02

Submission and updates are part of the job

We handle App Store and Play Store submission, including the review notes, privacy declarations and screenshots that hold most first submissions up. After launch, releases go out through an automated pipeline so a fix is hours away rather than a fortnight.

By market

What changes depending on where you trade

The build is not the same in every market. Tax, accessibility law and data rules differ, and they change the design rather than just the paperwork. Here is what shifts.

3 markets
US

For businesses in the United States

Apple and Google both require a privacy label describing exactly what your app collects, and both reject apps whose label does not match their behaviour. We fill those in from what the code actually does.

  • App Store privacy nutrition labels and Google Data Safety completed accurately
  • Apple Pay and Google Pay where you take payment in app
  • Push notifications through a US region service
  • COPPA handling if any part of the audience may be under 13
Working with us from the United States →
UK

For businesses in the United Kingdom

If your app takes payment for physical goods or services, Strong Customer Authentication applies, and getting the flow wrong shows up as abandoned checkouts rather than as an error message.

  • Strong Customer Authentication handled in the payment flow
  • Open Banking integration where it beats card fees
  • UK GDPR consent and clear in app privacy information
  • Age verification for age restricted goods
Working with us from the United Kingdom →
EU

For businesses in Europe

European users expect the app in their own language, and the Digital Markets Act has begun to change what is allowed on iOS in the EU, including alternative distribution. Worth knowing before you plan a launch.

  • Multi language from the first release, not a later update
  • PSD2 Strong Customer Authentication in payment flows
  • GDPR consent, data export and deletion available in app
  • EU hosted backend with a data processing agreement
Working with us from Europe →
Questions

Questions we get asked about this

3 answers
Q1 Native or cross platform?
Cross platform for most business apps, because one codebase means one set of changes forever. Native when you genuinely need deep hardware access or the last few percent of performance. We tell you which case you are in during scoping.
Q2 Who owns the App Store and Play Store listings?
You do. The apps are published under your developer accounts, not ours, so you are never locked to us for a release.
Q3 What happens when Apple or Google changes the rules?
Both push breaking changes on their own schedule. A support plan covers keeping the app compliant and shipping, which is the part people forget to budget for.
Next step

Tell us the problem. We send back a plan in 48 hours.

A written plan with every screen mapped, a fixed price and a delivery date. Yours to keep whether or not you hire us.

Related services

Often built alongside this

  • Web DevelopmentA website that takes four seconds to load on a phone has already lost most of the people who clicked. We build sites your team can edit, that pass Core Web Vitals, and that are structured so search engines can actually read them.
  • POS SystemsMost point of sale failures are not software bugs. They are a queue at the counter because the connection dropped. We build tills that run locally and sync when the line returns, so trading never stops.
  • ERP SoftwareOff the shelf ERP asks you to change your process to match the software. We do it the other way round. You get the modules you actually need, wired to the tools you already pay for, at a price agreed before anyone writes code.
WhatsApp us