Your service ready for both app stores
Sounds familiar? Our customers want an app on their phone, and our website can't do what they need.
People who use a service every week often want it a tap away, with notifications and screens that still load on a weak signal. Mobile developers build yours for iOS and Android, as two native apps or from one shared codebase. They test it on real devices and take it through App Store and Google Play review. Discovery and approved screen designs come before the proposal, because the features decide which approach fits and what it costs. Store accounts are set up for your business where Apple and Google allow, and the handover covers logins, files and documentation plus a plan for updates.

What you get
- Platform recommendation, native or cross-platform (one codebase for both), with the reasons
- iOS and Android builds in phases, each ending with a review on your own phone
- Sign-in and push notifications as scoped, plus the in-app account deletion both stores require for apps with accounts
- Back end (the server and database the app talks to), where the scope includes one
- Test versions shared through TestFlight (Apple) and Google Play testing
- Store listings and the privacy answers each store asks for, prepared with you
- Source code and release notes, with store account access documented for handover
- Release and update plan for new phone operating system versions
Is this right for you?
- You need an app customers install from the App Store or Google Play
- You need phone features such as the camera, location, notifications or offline use
- You have a web product, and regular users are asking for a phone app
- You have approved designs and need developers to build, test and publish
What it changes
Live in both stores
Once Apple and Google approve it, your app is live on store accounts set up for your business where the stores allow.
Tested on the phones people carry
Builds were tried on a range of phone models and system versions, and what testers found was fixed or logged before release.
A plan for the next update
The update plan lists what to check when Apple or Google release a new operating system or change a store rule.
Scope and delivery
How we deliver it, what we need from you, what is not included. Timeline: Estimated after an assessment
How we deliver it
-
Choose native or cross-platform
The technical lead weighs two native apps against one shared codebase. The choice rests on your features and budget, and on the phones your customers use.
-
Build the app and its back end
Screens, sign-in, notifications and data arrive in phases. Each phase ends with a review of a test build on your own phone.
-
Beta test on real devices
Testers install pre-release builds through TestFlight and Google Play testing. Problems that appear only on certain phones or system versions get fixed.
-
Submit to the stores
Listings and privacy answers are prepared with you before the apps go to Apple and Google for review. If a reviewer sends an app back, the developers work through the feedback and resubmit.
What we need from you
- Approved designs, or a written scope of the screens and features
- Apple and Google Play developer accounts for your business, or time to register them
- Store listing details: app name, support contact and a privacy policy link
- Beta testers from your team or your customers
What's not included
Complex work that is estimated only after a technical or business assessment.
Not included
- Apple and Google developer program fees, which you pay to the stores directly
- A fixed price or dates before the features and screens are agreed (see Product discovery & scoping)
- Back-end systems outside the agreed scope (see Custom web applications or System integrations & APIs)
Limits to know
- Apple and Google decide whether an app is approved and how long review takes. A first submission can be sent back for changes.
- Your privacy policy and the privacy answers in your store listings are statements your business makes. We help prepare them, and that help is not legal advice.
Where it fits
What usually follows, what may already be in place, and what is planned alongside, with the reason for each.
This service: Mobile app development
4 connected services
You may already have this
Skip it if it's already in place.
-
Product discovery & scoping
Features and users agreed in writing.
-
UI/UX design
Screens are approved before code.
Keeps it running
Keeps it working after launch.
-
App support & maintenance
Phone operating system updates can break apps that nobody maintains.
Part of these packages
-
Digital product & MVP launch
Optional add-on: When the first version must be a phone app.
Read before you decide
Common questions
Should we build native or cross-platform?
Cross-platform frameworks such as React Native or Flutter run one codebase on iOS and Android, which suits many business apps. Native development makes sense for heavy graphics, complex hardware use or early access to each platform's newest features.
Whose App Store and Google Play accounts are used?
Apple and Google each require a developer account, and you pay their fees directly. The accounts are set up for your business where the stores allow. A company account needs a D-U-N-S number, a business identifier, unless it belongs to a government body. Apple says to allow up to 5 business days for one, and Google says it can take up to 30 days, so it is worth applying early.
How long does app store review take?
Apple and Google set their own review times, and they vary. First submissions are sometimes sent back over policy issues, so the plan leaves room for a round of fixes before your launch date.
What happens when iOS or Android updates?
New operating system versions can break features or bring new store rules. App support & maintenance covers testing and updating the app for each one, and Testing & QA can check every store release on real devices.