Do you build native or cross-platform?
Usually React Native or Flutter, because one codebase for both platforms costs less to build and much less to maintain. We go fully native when the app needs deep hardware access or heavy graphics, and we tell you which it is during scoping rather than after. Our guide to mobile app development walks through the trade-offs in more detail.
Who owns the code and the store accounts?
You do, from day one. We work in your GitHub organisation and publish under your Apple and Google developer accounts. If you part ways with us, nothing needs migrating.
What if Apple rejects the app?
We handle it. Rejections are normal on a first submission. We deal with the review notes and resubmit at no extra cost, because it is in the fixed price.
Can you take over an app someone else built?
Often yes. We start with a paid audit of the existing codebase and give you an honest answer about whether it is worth continuing or rebuilding. Sometimes the answer is rebuild, and we will say so with reasons.
How long until we can put it in front of users?
You are testing on a real device from week two. Store launch is typically eight weeks for a focused app and longer for something with payments and multiple user types.
What happens after the 30 days of support?
Either your team runs it, which is what the handover session is for, or you move to a monthly retainer for updates and OS version changes. No lock-in either way.
