What we do
Tools
Industries
Department
How we workLet's talk →
Home/Flutter Developer for One App on Two Stores
Flutter Development

Hiring a Flutter Developer for One Codebase That Has to Pass Two App Stores

Flutter lets one Dart codebase run as an iPhone app and an Android app, and that really does bring the build much closer to one app than two. What it doesn't merge is everything around the code: two stores with their own review rules, two sets of native settings, and plugins that each platform treats differently. A good Flutter developer is mostly judged on those parts.

What one Flutter codebase covers, and what stays doubled

Shared

Written once in Dart

  • Screens, layout and navigation.
  • Business rules: pricing, validation, what each user is allowed to do.
  • Calls to your backend and the handling of its data.
  • Most tests, which run the same against both platforms.
Per platform

Still done twice

  • Store listings, screenshots, privacy disclosures and review, once with Apple and once with Google.
  • Signing certificates, bundle IDs and app keys, each stored safely by someone you trust.
  • Native settings: Info.plist on iOS, the Android manifest and Gradle files on Android.
  • Push notifications, in-app purchases and permissions, which run on each platform's own services.
  • Testing on real devices of both kinds, because a simulator hides a lot.

Budget the right-hand column as real work. It's where a quote that only counted screens comes up short.

Getting one Flutter build through both stores

The order that avoids last-minute surprises on release week.

  1. 1

    Open both developer accounts in your company name

    An Apple Developer Program membership and a Google Play Console account, owned by the business, with the developer invited as a team member. Apps published under a freelancer's personal account are painful to move later.

  2. 2

    Set up signing once, and keep the keys safe

    iOS builds need certificates and provisioning profiles, made in Xcode on a Mac. Android needs an upload key. Losing access to these is one of the few mistakes that can block updates entirely, so store them where more than one person can reach them.

  3. 3

    Test on real phones through each store's beta channel

    TestFlight on iOS and an internal or closed testing track on Google Play. Testers install the same build the public will get, which catches signing and permission problems a debug build hides.

  4. 4

    Fill in the privacy answers carefully

    Apple's privacy details and Google Play's data safety form ask what data the app collects and why. They have to match what the app and every plugin in it actually do, including analytics and crash reporting packages.

    Watch for: a plugin that collects device data you didn't know about. Reviewers check, and a mismatch can hold up a release.

  5. 5

    Release gradually

    Google Play can roll an update out to a percentage of users, and the App Store can phase automatic updates over several days. If a crash report spikes, you can pause before everyone has it.

Where Flutter apps break on one platform and not the other

Native features such as the camera, location, payments and Bluetooth come through plugins, and each plugin is really two pieces of native code with one Dart face.

The app crashes the moment an iPhone user opens the camera

How you'll know: Fine on Android, and an instant close on iOS when the feature is first used.

Fix: iOS needs a written usage description in Info.plist for the camera, photo library, location and similar. Without it the app is closed by the system, and App Review rejects it. Each plugin's setup notes list the keys it needs.

A plugin only really supports one platform

How you'll know: It installs fine, but a feature does nothing on one platform, or throws a missing-implementation error.

Fix: Check the platforms listed for the package on pub.dev, and read its open issues before depending on it. Where no good plugin exists, the developer writes the native piece and calls it through a platform channel.

The build stops working after nobody touched it for a year

How you'll know: A small text change won't compile, or a store refuses the upload.

Fix: Apple raises the minimum Xcode and SDK for new uploads, and Google Play raises the Android version apps must target. Updating the Flutter SDK, the plugins and the native build files together, then testing both platforms, is a planned job rather than an emergency if you do it once a year.

One abandoned plugin holds the whole app back

How you'll know: You can't update Flutter because one package hasn't been updated to work with it.

Fix: Replace it, take over a copy of it, or write that feature natively. Keeping the plugin list short from the start makes this rare.

Let's talk

A Flutter app built and kept shipping on both platforms

n-frames builds Flutter apps that connect to the systems a business already runs on, like bookings, orders, a CRM or a custom backend, and keeps them publishing as both stores change their requirements. Every release is tested on real iPhone and Android devices before it goes out, under developer accounts in your name. If the app needs a feature Flutter can't reach well, we write that piece natively rather than forcing a workaround.

Cost our two-store Flutter build →

Questions people ask

Should we build native apps instead of Flutter?

Usually not, if the app is mostly screens, forms and data from your backend. Native is worth it when the app lives on one platform's newest features, heavy graphics or deep hardware work. A middle path is Flutter for the app with small native pieces where needed. iOS developer and Android developer cover the fully native routes, and React Native developer the other main cross-platform option.

What happens when a Flutter plugin breaks on one platform only?

We find out whether it's the plugin's native code, a missing setting on that platform, or a version clash with Flutter itself, then fix or replace it and retest on both platforms. A fix checked only on the platform that broke is how the other one breaks next.

Can you take over an existing Flutter app from a freelancer who's gone quiet?

Yes. First we get it building from the source on a clean machine for both platforms, and confirm you control the developer accounts and signing keys. Then we update what's outdated, starting with whatever the stores will refuse soonest.

Whose developer accounts should the apps be published under?

Yours. The Apple and Google accounts, the signing keys and the app listings should belong to the business, with developers added as team members you can remove.

Can the same Flutter code also run as a web app?

Flutter does build for the web, which suits an app-like tool behind a login. For a public site that needs to rank in search and load fast on a first visit, a normal website is the better choice. Planning the wider product, including the backend, is on mobile app developer.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.