Mobile apps
Android and iOS apps built from a single Flutter codebase — designed, shipped to the stores and kept alive after launch. You get the repository, the signing keys and a release process you can run yourself.
What the work covers
Everything between the idea and an app that a stranger can install and understand without being told how.
One codebase, two stores
Flutter gives Android and iOS from the same source. One bug is fixed once, one feature is written once, and the two platforms stay in step instead of drifting apart.
Offline as a default
The app opens and works without signal. Data is written locally first and synced when the connection returns — not the other way round.
Push and deep links
Notifications that reach the right screen, links that open the app instead of the browser, and the routing that makes both dependable.
Store submission
Signed builds, store listings, screenshots, age ratings and the Data Safety form. We handle review rejections and resubmit until it is live.
Account and data deletion
The in-app deletion flow Google Play requires, plus the public page that backs it. Built in from the start, not bolted on before review.
Crash and usage visibility
Crash reporting and basic analytics wired up before launch, so the first bad release is caught by you and not by a one-star review.
What you end up with
- A Git repository you own, with the full history and no vendor lock-in.
- Signed release builds plus the keystore and certificates, handed over to your own accounts.
- A store listing that passed review, with the Data Safety and privacy declarations filled in.
- A short written handover: how to build, how to release, and what to watch after a deploy.
The stack we reach for
- Flutter
- Dart
- Material 3
- Supabase
- PostgreSQL
- Firebase
- Google Play Console
- App Store Connect
How it runs
Scoping
We map the screens, the data and the edge cases, then agree what the first release has to do — and what it deliberately will not.
Build in cycles
Installable builds land with you every couple of weeks. You use the app on your own phone long before it reaches a store.
Store release
Signing, listing, review. We deal with the rejections and the back-and-forth until the app is published.
After launch
Crash monitoring, store feedback and the next versions — the part where most apps quietly go stale.
Questions we get asked
Do I own the code?
Yes. The repository is yours from the first commit, along with the signing keys and the store accounts. There is nothing you need our permission to keep running.
Can you publish under my company account?
That is the arrangement we prefer. Your Google Play and App Store accounts stay yours; we get the access we need to publish and hand it back whenever you ask.
What about an app that already exists?
We take those on. The first step is a short read of the codebase and a written note on what is solid, what is risky and what it would cost to move forward.