What We Build with Flutter
- new iOS and Android apps from a single codebase, from screen design to publishing in both stores;
- apps with branded design, custom animations, charts and non-standard elements;
- apps with user accounts, catalogs, payments, push notifications and maps;
- companion tools for internal use, for example a mobile app for couriers and a dispatcher dashboard sharing the same logic.
When Another Tool Is a Better Fit
- Your web product is already built in React and you have developers maintaining it: React Native is the smarter choice, because you can reuse some of the code and know-how.
- The app relies heavily on the camera, audio, augmented reality or background processes: separate native apps are more reliable.
- You only need convenient mobile access to your website without publishing to app stores: consider a progressive web app.
- You need a public content website where fast loading and SEO matter: we recommend separate web development rather than Flutter for web.
Packages and Native Modules
Flutter has ready-made packages for most common tasks: payments, maps, notifications, Google and Apple sign-in, analytics, Firebase. But "there's a package" doesn't mean "it's safe to use." We check who maintains it, how often it is updated, whether it works with the current Flutter version and whether it has known issues.
If there's no reliable package, we write our own native module, a Swift part for iOS and a Kotlin part for Android, and connect it to the shared code. That's how we integrate, for example, specific payment terminals or third-party SDKs that have no Flutter version.
Code Structure for Growing Apps
We choose the approach to state management based on the size of the product: lighter solutions for simple apps, stricter separation of UI, logic and data for large ones. That way new developers get up to speed faster, and changing one screen doesn't break the others.
New Project or Improving an Existing One
A new app starts with a design system: colors, fonts, buttons, fields and cards first become a set of custom widgets. After that, screens come together faster, and style changes are made in one place.
An existing Flutter project often comes to us in a "hasn't been updated in ages" state. Flutter evolves quickly, and an app that went several years without updates may no longer build with current Apple and Google tooling. We assess which packages are outdated and what will change during the upgrade, then migrate the project to the latest version step by step.
What to Prepare Before Kickoff
- A description of the app's features and your target users, or your existing design files.
- API documentation, or a note that the backend still has to be built.
- Developer accounts for the App Store and Google Play, or a decision on who will create them.
- For an existing app: repository access and the Flutter version in use.
What Affects the Cost
- Design: standard Material Design components or a fully custom branded interface with animations.
- Native modules: how many features aren't covered by existing packages.
- Backend: an existing API that just needs to be connected, or new backend development.
- Platforms: phones only, or also tablets, a web version or a desktop app.
- State of an existing project: for upgrades, the Flutter version, the number of outdated packages, whether there are tests.
We provide an estimate after reviewing your project, with the work broken down into clear phases.
Frequently asked questions
Is Flutter suitable for large apps? Yes, if a clear project structure and state management are in place from the start. Problems in large Flutter apps usually stem from architecture, not from the tool itself.
Will the iOS app look like an Android app? Not if the design is thought through for both platforms. You can use a single brand style or show platform-native elements where it matters.
Can you update an old Flutter project built by another team? Yes. We start by auditing the code, versions and packages, then propose an upgrade plan.
Can the same code also produce a web or desktop version? Yes, from the same codebase, which is handy for internal tools. Whether it makes sense depends on the project, and we say so upfront.
Will you publish the app to the stores? Yes. We publish to the App Store and Google Play and schedule regular updates of Flutter and the packages used.
Do you test on real devices? Yes. We check the UI on real iOS and Android devices, including older and low-end ones, and test the logic with automated tests as the project requires.
Why Promodex
Since 2015, Promodex has delivered 750+ projects. The mobile apps we have worked on include My Viva and MyAmeria. Design and development are handled by our in-house team with no subcontractors, so the designer and the Flutter developer discuss every screen directly. After launch, we help with app support and ongoing development: updating Flutter and packages, adding features and monitoring stability.