Apollo Tech Studio
Talk to an engineer

Flutter

Flutter app development, from first build to the next store release

We build Flutter apps for iOS and Android, take over Flutter codebases other teams left, and keep them shipping. Three of the apps we run in production today are Flutter: a dealer app, a two-sided inspection marketplace and a buyer-and-dealer app for a vehicle importer.

Talk to an engineerSee the work

What we do with Flutter

  • New apps

    One Dart codebase for iOS and Android: sign-in, push that opens the right screen, payments, maps, camera, offline storage, and the admin or backend the app needs.

  • Takeovers

    A Flutter app another team started and did not finish. We read it first, then decide with you what to keep and what to rewrite. On Qovo that meant a new app written from scratch on the backend that was worth keeping.

  • Upgrades

    Old Flutter and Dart versions, deprecated packages and store target-SDK deadlines. We move the app forward in steps and keep it releasable between them.

  • Releases and care

    App Store and Google Play releases from CI, staged rollouts, crash tracking, and a monthly arrangement that keeps the app current after launch.

Flutter apps we built and run

Each one is live and each one is ours to release. The case pages show the screens.

How our Flutter apps are put together

What the apps above have in common, taken from their codebases.

  • Store releases come from CI with fastlane, with release notes taken from the changelog.
  • Google Play production goes out as a staged rollout, not to everyone at once.
  • Crashes are tracked in Sentry.
  • Push notifications open the screen they are about.
  • Biometric unlock of the stored session: Face ID, Touch ID or fingerprint.
  • Minimum version, forced update and maintenance mode can be switched from the server, without a release.
  • End-to-end flows in Maestro cover the main user paths.
  • State management follows the app: Riverpod on one, MobX on two others.

How work starts

  1. 1. A free call

    Tell us what the app is, where it is stuck and what has to ship next. Nobody reviews code on the call.

  2. 2. A fixed-price code audit

    For an existing app: we read the code, the build setup and the store accounts, and deliver a written report in 5 working days — what builds, what breaks, what is risky and a priced plan.

  3. 3. The work

    A fixed-scope sprint to get the app to production, or a scoped build for a new app.

  4. 4. Care

    After launch, a monthly arrangement for OS and SDK updates, store deadlines, monitoring and small features.

Questions about Flutter development

Can you take over a Flutter app another team wrote?

Yes. We start with a code audit, then decide with you what to keep. Qovo is an example: the first version came from Builder.ai, which went insolvent in 2025; we kept and extended its Rails backend and wrote a new Flutter app on top of it.

Do you publish to the App Store and Google Play for us?

Yes. Our Flutter apps ship to both stores from CI with fastlane, and Google Play releases go out as staged rollouts.

Which state management do you use?

The one that fits the app, and the one it already uses if it is sound. The apps we run use Riverpod and MobX.

Do you also build the backend?

Yes. The apps above run on Laravel and Ruby on Rails backends we build or run as well.

Can a Flutter app keep up with the yearly Android and iOS changes?

Yes, if someone keeps it current. Our guide to the Google Play target API 36 requirement covers what the latest Android change means for Flutter apps.

Next step

30 minutes with an engineer, not a sales rep. You leave knowing what we'd fix first — or that you don't need us.

The first call is free. A code audit of an existing Flutter app is a fixed price from $750, credited against the work if you continue within 30 days.

Show us what's stuck[email protected]