Product scoping
What the app must do in its first version, what it will not do, and how we will measure that it is useful. An app that tries to do everything at launch never launches.
An iOS and Android app, published and maintained by the people who built it.
We build on Flutter: one codebase, two native apps, published on the App Store and Google Play. Swapp and Georgia, our own apps, are built this way and have been maintained since launch.
What is delivered.
A published app, not a prototype.
Screen design
Flows and screens drawn on the iOS and Android templates, with the real states: loading, empty, error, offline. Those states are the difference between an app that looks finished and one that is.
Flutter development
One codebase, two native apps. Backend on Supabase or Firebase depending on the need, payments through Stripe if the app sells anything.
Publishing on the stores
Developer accounts, listings, screenshots, privacy policy, passing Apple and Google review. We have done it for our own apps; we know the reasons for rejection.
Maintenance after launch
New iOS and Android versions, fixes, crash monitoring, improvements. An unmaintained app is pulled from the stores in under two years.
How it runs.
In order of magnitude, 8 to 14 weeks from the first meeting to publication on the stores. This is not a contractual commitment; the firm schedule is set during scoping.
- 1
Scoping
one weekScope of the first version, choice of backend, publishing schedule.
- 2
Design
one to two weeksFlows, screens, states. A clickable prototype tested on a phone before a line of code.
- 3
Development
five to ten weeks depending on scopeTest builds distributed to your phones every week through TestFlight and Play Console.
- 4
Publishing
one to two weeks, store review includedSubmission, store review, requested fixes, release.
- 5
Monitoring
ongoingCrashes, user feedback, system updates. A monthly maintenance contract.
Our own apps are the proof.
We do not show mockups: we show apps you can install.
Swapp
A digital business card, iOS and Android. Published, maintained, used. [figures to be added]
See SwappGeorgia
Career and finance management for models. The same Flutter codebase, the same publishing pipeline.
See GeorgiaWhat that changes for you
We know what an app costs after release: the system updates, the review rejections, the Monday crashes. We plan for them in the quote instead of discovering them with you.
Frequently asked questions.
Why Flutter rather than native?
A single codebase for iOS and Android halves the cost of development and maintenance, with native performance. Our own apps run on it.
Do we need an Apple and Google developer account?
Yes, in your name. We create them with you: the app belongs to you, including its store listing.
What happens if Apple rejects the app?
We fix and resubmit; that is included. The common reasons for rejection are known and anticipated from the design stage.
Can you take over an existing app?
Yes, after a code audit. If taking it over costs more than a rewrite, we tell you, with figures.
An app to build?
Describe what it must do in its first version and who it is for. We reply within two working days.