Native iOS and Android
- Two store binaries when the product needs platform-specific behaviour.
Mobile app development
Mobile app developmentiOS, Android, and cross-platform apps, including the backend, under your agency name.
A defined mobile product for a client you already hold: native or cross-platform, with the API and data work the app needs. You keep the relationship. We never contact the client. Design can sit in this order, or you can bring approved screens.
What the app is for
The store listing, the binaries, and the admin sit in your handover. The client still sees you as the studio that shipped it.
- 01
iOS and Android
Native where the brief needs it, or one cross-platform codebase when that is the better fit.
- 02
The backend included
The API, auth, and data the app cannot live without, named in the quote. A separate enterprise platform is a different conversation.
- 03
A store-ready build
TestFlight, Play internal testing, then the files you need to submit. Store accounts stay in the client's name unless you say otherwise.
- 04
You run the relationship
Reviews, store answers, and the launch email come from you. We stay in your tools.
- 05
Room to grow
Later features are new quotes. The first release is the jobs listed in the brief, not an infinite backlog.
How agencies order the build
Pick the delivery that matches the product. Mixing them is fine when the quote says so.
Cross-platform
- One codebase for both stores when the jobs are the same on each phone.
Backend with the app
- API, auth, and data for the screens in the brief.
- Hosting is the host named in the quote.
How it runs
From the jobs to a build you can submit
You approve screens before we spend the engineering weeks. Quality check is done in Europe.
How revision rounds work
The jobs in the brief, on the platforms you named, with the quoted design and build rounds.
A new job, a second product, store ads, or a full redesign after sign-off is a new quote.
What we do, and what we need from you
Mobile work waits on store accounts, certificates, and the jobs. This is the split.
| Task | Your agency |  |
|---|---|---|
| We scope platforms, backend, and whether design is included. | ||
| We build the jobs in the brief and give you test builds. | ||
| We prepare the store files and the notes for submission. | ||
| We never contact your client. | ||
| Apple and Google accounts, or a decision that you will create them. | ||
| The jobs the first release must do, and any existing design files. | ||
| Content, legal copy, and privacy text the stores will ask for. | ||
| Someone who can test on a phone and who speaks to the client. |
Reseller-ready on purpose
Contracts, invoices, and store listings stay in your name. We are capacity behind your studio, not a second vendor on the call. The client never sees another engineering brand, including in TestFlight or Play test tracks unless you put it there.
Design can be in or out
Bring approved screens from App & UI/UX Design, or put design in this quote. Either way, screens are signed before production builds. Mixing them is fine when the quote says so; unsigned screens do not start the engineering weeks.
Hourly support is later
Fixes after launch can sit on Ad-hoc Development Support. The first release is this project: the jobs in the brief, on the stores you named, through the quoted rounds. A named person every week is Dedicated Resources, not this page.
Agencies often add these extra services
From the blog
Notes that sit next to this work. All notes
Web Design & Dev
Progressive Web Apps
What progressive web apps are, how they compare with native apps and when a PWA is the right choice for a client's project.
2 min read
Frequently asked questions
Agencies that want to sell iOS, Android, or cross-platform apps, including backend, under their own name.
Ready to brief a mobile app?
Name the jobs and the stores. We build it behind your brand, including the backend it needs.