Industries/ Startups/ Phone apps and store launch
Mobile app development with the store paperwork done in parallel.
We build your app for iPhone and Android together and start the developer accounts, testing tracks and privacy declarations while the app is still being built. The launch date you announce is set from the real constraints, not from hope.

- Used by
- Your customers, the founders and whoever handles support
- Takes the place of
- A mobile website and a submission scramble before launch
- Connects to
- Your back end, sign-in, push notifications and both stores
- Built with
- Our app store launch service
Where it hurts today
A normal week, before it exists
The app is nearly finished and a launch date has been mentioned to investors, a pilot customer and a newsletter list. Then the founders discover that the stores are their own project. Apple wants a verified organisation with a D-U-N-S number. Google Play wants its own verification, and some new accounts must run a closed test before they can publish to everyone. None of it cares how finished the app is.
The submission itself is full of small traps. A privacy declaration filled in from memory does not match what an analytics library inside the app actually collects. The reviewer cannot get past the sign-in screen because nobody gave them a test account. Screenshots are needed at sizes nobody exported. Each rejection means a fix and another trip through review, while the announced date gets closer.
Before any of that, there is the question of whether the product needs an app yet at all. Some do: they need the camera, notifications, offline use or a place on the home screen. Others would be better served by a fast mobile website for another year, because an app built too early doubles what the team must maintain while the core product is still changing.
What it does
Phone apps and store launch, feature by feature
The app and its launch, run as one piece of work rather than two in sequence.
- 01
iPhone and Android apps built together
One shared codebase for both platforms where the product suits it, with native code only where a feature genuinely needs it, such as the camera, payments or background location. One team, one set of tests and one release rhythm instead of two versions drifting apart.
- 02
Developer accounts started on day one
Apple Developer Program and Google Play Console set up as your company, with the legal entity checks and D-U-N-S number started first, because they can take longer than the build. Roles are set so contractors get the access they need and nothing more.
- 03
Privacy labels written from the code
Apple's privacy labels and privacy manifests, and Google Play's data safety form, are completed from an audit of what the app and every library inside it collects and sends. If a library collects more than you are comfortable declaring, you decide before submission, not after a rejection.
- 04
TestFlight and closed testing first
TestFlight on iPhone and closed testing on Google Play, with pilot customers and friendly users organised as testers. Feedback and crash reports land in one place, and any testing period a new Google Play account needs runs while the app is still being finished.
- 05
App Store review notes and a demo account
Every submission goes in with a working test login, sample data and short notes explaining anything a reviewer might misread, such as why the app asks for the camera. When a rejection is a misreading, we answer it through the store's resolution process with the relevant guideline and evidence.
- 06
A phased release with a way back
Both stores can release an update to a share of users first. We watch crash rates and start-up times against a threshold you agree, and pause the rollout if a build misbehaves, so a bad release reaches some of your users rather than all of them.
A day with it
How the day runs instead
A normal week in the run-up to launch, with the app in testing and the store side moving at the same time.
- MondayFounder
The founder opens the launch checklist. The Apple organisation is verified, the Google Play closed test is running, and one item is red: the privacy declaration does not match a newly added analytics library. It has an owner and a note explaining the fix.
- TuesdayPilot customer
A pilot customer installs the latest beta through TestFlight, runs through sign-up and the core task, and reports a button hidden behind the keyboard on a small phone. The report arrives with a screenshot and the device model attached.
- WednesdayEngineer
The engineer fixes the keyboard issue, and the build pipeline signs and uploads a new version to both test tracks without anyone handling certificates on a laptop. Testers are notified automatically and the old build stops being offered.
- ThursdayMarketing lead
The marketing lead reviews the store listings: title, subtitle, description, keywords and screenshots generated from the latest build at every required size. The wording matches the website and the brand guide, and the preview video is approved.
- FridayFounder
The build goes to both stores with reviewer notes and a demo login, set to release to a share of users first once approved. The founder now knows which date can be announced and which step still depends on review.
What it connects to
Works with what you already run
A phone app is usually a new front end on a product you already have, so most of its connections are ones you already run.
Your existing back end
The app reads and writes through the same API as your web product, so customers see the same accounts, data and permissions on both. Where no clean API exists yet, building one is part of the work.
Sign-in
Email, passkeys or single sign-on through your existing provider. If the app offers Google or another social login for the main account, Apple's guideline 4.8 asks for an equivalent privacy-focused option alongside it, which Sign in with Apple provides.
Push notifications
Notifications sent through Apple's and Google's push services, triggered by events in your product, with the permission request explained in plain words at the moment it makes sense.
In-app purchases and billing
Where store rules require their own billing for digital subscriptions, purchases go through it and sync back to your billing records, so a customer's plan is the same on the phone and on the web.
The first version
Start small, then grow it
A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.
In the first version
- The core flow on iPhone and Android from one shared codebase
- Developer accounts set up and verified in your company's name
- Privacy labels and the data safety form written from a code audit
- Beta testing with pilot customers on both platforms
- Store listings, reviewer notes and a phased first release
Once it is in use
- Push notifications tuned to what customers actually respond to
- Offline use for the parts of the app people need without signal
- Localised store listings for new markets as you expand
- Home screen widgets or watch support if customers ask for them
Buyer's guide
Before you commission one
Four decisions worth making before you commission an app.
- 01
Mobile website, app builder or custom app
A fast mobile website or a progressive web app is often enough while the product is still changing. App builders and no-code platforms can work well for simple content or booking apps. A custom app earns its place when you need the camera, notifications, offline use, device sensors or a home screen presence that customers actually ask for.
- 02
What to prepare first
Your company's legal name and registration details exactly as they appear officially, a D-U-N-S number or the details to request one, a company email and phone number for store listings, a privacy policy URL, and a list of every analytics, crash reporting and advertising library you plan to include in the app.
- 03
Who should own it
One founder should hold the developer accounts as account holder, since that role signs agreements and controls access. A product lead should own release decisions and the rollout. Someone should own store reviews and replies, because ratings arrive from the first day and early replies set the tone for every reader after them.
- 04
How you will know it is working
Watch crash-free sessions per release, how many new users finish sign-up on the phone, whether they return the following week, ratings and the themes in written reviews, and whether people use the features that justified an app in the first place. If they only use what the website already offers, that is worth knowing.
Terms worth knowing
The words you will meet
- D-U-N-S number
- A company identifier issued by Dun and Bradstreet. Apple uses it to verify a company's legal identity before the company can publish apps under its own name. Your company may already have one, so we check before requesting a new one, and we start early because it can hold up the developer account.
- Privacy manifest
- A file inside an iPhone app that declares what data the app and its third-party libraries collect, and why certain system features are used. Apple has required them for commonly used third-party SDKs since 1 May 2024. Google Play's counterpart is the data safety form, and both must match what the code actually does.
- Closed testing
- A test track that releases your app to named testers before the public. On Google Play, personal developer accounts created after 13 November 2023 must run a closed test with at least twelve testers for fourteen days before publishing to production. Registering as an organisation follows a different verification route.
Handled with care
The details that matter here
The stores are gatekeepers, and app users judge quickly. These are the details we handle carefully.
Listings owned by your company
Both developer accounts are registered to your company, with us added as members whose access you can remove at any time. In the EU, Apple shows trader contact details under the Digital Services Act and has removed apps without trader status there since 17 February 2025, so we settle those details first.
Account deletion done properly
Apple requires apps that let people create an account to let them delete it from inside the app, and Google Play also asks for a web link where deletion can be requested. We build both so deletion actually removes the data, and design the flow around UK GDPR and EU GDPR with your data protection lead.
Accessible on small screens
We test with large text, screen readers on both platforms and small phones. WCAG 2.2 sets a minimum target size for tappable controls, and in the EU the European Accessibility Act has applied since 28 June 2025 to certain consumer services, such as online shops, with an exemption for microenterprises. We review which rules apply with you.
Keeping up with store deadlines
Both stores raise their minimum requirements regularly. Since 28 April 2026, Apple has required uploads built with Xcode 26 and the iOS 26 SDK, and since 31 August 2026, Google Play has required new apps and updates to target Android 16. We plan these into support, so a deadline is a calendar entry, not a removal notice.
Guides
Worth reading first
Questions
What buyers ask first
Does my startup need a mobile app yet?
Not always, and we will tell you if you do not. An app earns its place when the product needs the camera, notifications, offline use or a spot on the home screen, or when customers keep asking for one. If your product works well as a fast mobile website, that may serve you better for now, and it keeps the team focused on one surface while the product is still changing.
What do you need to publish an app on the App Store and Google Play?
A developer account on each store in your company's name, which for Apple means a verified organisation with a D-U-N-S number. Then a privacy policy, privacy declarations that match the code, an age rating, store listings with screenshots at the required sizes, and a test account for reviewers. On the App Store you also declare whether you are a trader under the EU Digital Services Act. We prepare all of it alongside the build.
What happens if Apple rejects our app?
Rejections happen, and most are fixable. Some are fair, such as a missing explanation for a permission. Some are a reviewer's misreading. We answer through the store's resolution process with the relevant guideline and evidence, change the app where the objection is right, and escalate where it is not. Submitting with clear notes and a working demo account avoids many of them in the first place.
Do we have to use in-app purchases for subscriptions?
Often, for digital subscriptions bought inside the app, but the rules differ by region. On Apple's US storefront, apps may now include buttons or links to buy through your own website. In most other storefronts that is restricted unless a specific entitlement applies, and Google Play has its own billing rules. We check the current guidelines for each market before designing the payment flow, because they have changed recently.
Can you take over an app another developer started?
Yes. We start by reviewing the code, the build setup and the store accounts, because an app often stalls on signing certificates or on an account registered to someone who has left. If a listing already exists, we publish into it so ratings and installs carry over. If the code is not worth keeping, we explain why in writing before suggesting anything else.
Planning to announce a launch date?
Tell us where the app stands and what date you have in mind. We will tell you what the stores will need and when to start, and we reply within 48 hours.
More for startups
What else we build for startups
Pitch-ready brand identity
A mark, colours, type and a pitch-deck template sized for where you are now, with room to extend later. Investors, first hires and early customers judge credibility on thin evidence, so give them a company that looks as considered as the product.
A narrow first release
One workflow, real accounts and real billing, built on foundations that will not need replacing. Small enough to ship early and put in front of paying customers, so what you build next is decided by what they actually do.
Finishing a stalled build
An honest assessment of the half-finished product you were left with, then the parts that matter stabilised, tested and completed. Rebuilding by reflex is expensive, and often the existing code needs finishing rather than replacing. We will tell you which.
AI inside your product
Smart search, recommendations, summaries or document reading built into your own product, each scoped to do one job well, with the cost per customer measured before the feature goes anywhere near your pricing page.
Metrics your board trusts
Signups, activation, retention, revenue and churn pulled straight from your product and billing system into one live view, so investor updates and board packs stop costing a founder a weekend of spreadsheet work.
