Flutter Mobile App Development: Full Cycle

Start with a concrete situation. A client brings a taxi aggregator concept: three roles, real-time updates, maps, background geodata. The requirement—60 fps even on budget devices and deployment to stores without rejections. Flutter covers 80% of the tasks here, but at the edges—BLE, background tasks, native SDKs—there's a 30% time penalty if you don't know the pitfalls. We know these pitfalls—over 8 years in mobile development, we've accumulated experience from dozens of projects. We'll assess your project for free in two days.

How Flutter Reduces Development Budget

Compared to separate development in Swift and Kotlin, Flutter saves 30–50% due to a single codebase, one language, and fewer bugs at platform boundaries. According to Google, Flutter outperforms React Native by 15–25% in frame drop rate. On a real project with 200k records in a local database, the difference between isar and hive was ~3x on filtering—real numbers, not promises. Development cost savings compared to native can reach 1.5–2x. For a typical MVP with 5–10 screens, the development cost with Flutter is approximately $20,000–$40,000, saving 30–50% compared to native, which means you save $15,000–$20,000.

Where Flutter Wins and Where Caution Is Needed

The cross-platform approach is justified when the UI logic is identical on iOS and Android and the product is needed quickly. Flutter covers 80–90% of needs through standard Material and Cupertino widgets. Problems start at the edges.

Platform-specific APIs. Bluetooth Low Energy—via flutter_blue_plus, but its behavior on Android 12+ (where Google changed permissions from ACCESS_FINE_LOCATION to BLUETOOTH_SCAN) requires separate handling. On iOS—a separate key NSBluetoothAlwaysUsageDescription in Info.plist plus background mode bluetooth-central. Miss this—the App Store will reject per guideline 5.1.1.

Background execution. Dart Isolates don't solve background tasks at the OS level. For background geolocation—use background_locator_2 + WorkManager on Android. On iOS—CLLocationManager in allowsBackgroundLocationUpdates mode. Here Flutter only provides a thin wrapper; the real logic is native.

Platform channels. When no ready plugin exists, we write a MethodChannel or EventChannel. A typical case—integration with a POS terminal via the manufacturer's SDK (Ingenico, PAX): the SDK is only available as .aar for Android and .framework for iOS, we wrap it in native code and pass it through the channel. Here 'cross-platform' ends exactly at the channel boundary.

How We Build Architecture

For projects with five or more screens, we use clean architecture with data, domain, presentation layers. State management—Riverpod 2.x (providers like AsyncNotifierProvider instead of the outdated ChangeNotifierProvider). We use BLoC when the team already works with it or when a strict event-driven flow with testable states is required.

Navigation—go_router 13.x with deep link support and web routing (if Flutter Web is needed). We avoid the old Navigator 1.0—with complex nested routes, the stack breaks unpredictably.

DI—via get_it + injectable. Code generation via build_runner reduces boilerplate but requires discipline: freezed for immutable models, json_serializable for serialization, drift or isar for local DB. isar version 3.x shows noticeably better performance than hive on collection operations—in one project with 200k records, the difference was 3x on filtering.

Real-world example. A taxi aggregator app—three user roles (passenger, driver, dispatcher), real-time updates via WebSocket (web_socket_channel), maps via flutter_map + OpenStreetMap tiles (the client saved on Google Maps SDK). Background driver location updates—via WorkManager on Android and BGAppRefreshTask on iOS, wrapped in Dart. Release build—Fastlane + GitHub Actions: a single workflow builds --release APK and IPA in parallel, signs, and uploads to Firebase App Distribution for QA.

State management comparison:

Testing and CI

Unit tests in Dart—standard flutter_test. Integration tests—integration_test package (run on real device or emulator via flutter drive). Widget tests cover key components: testWidgets with WidgetTester and pump/pumpAndSettle.

In CI (GitHub Actions / GitLab CI), we separate: flutter analyze + dart format --set-exit-if-changed on every PR, tests run in parallel on Android API 33 emulator and iOS Simulator. Builds for TestFlight and Google Play Internal Track—via Fastlane Match for certificates.

We profile performance in flutter run --profile + DevTools: Timeline view shows jank frames (>16ms), Memory view shows heap between rebuilds. Typical issues: excessive setState in deep trees, unoptimized images (decode without cacheWidth/cacheHeight), expensive computations in build() instead of extracted compute().

What's Included

1. Requirement analysis and technical specification (1–2 days)
2. UI prototype and architecture design (1–2 weeks)
3. Business logic and API integration (core sprint)
4. Native plugin development (if needed)
5. CI/CD setup via GitHub Actions
6. App store submission support
7. Post-release support (2 months)

Common Mistakes in Self-Development

We most often see three problems when auditing Flutter projects from other teams.

1. Incorrect provider architecture. ChangeNotifier with global state that rebuilds the entire screen on any change. Switching to Riverpod with granular select calls solves the problem but requires refactoring.

2. Platform channel without error handling. Native code throws an exception → the channel fails → the app crashes without a clear message. We wrap all MethodChannel calls in try/catch PlatformException.

3. Ignoring isolates for heavy operations. JSON deserialization of a 10MB response on the main isolate causes noticeable freezes. compute() or manual Isolate.spawn is mandatory for data >1MB.

Timelines

Our Company Metrics

With 8+ years of mobile development experience and over 50 successful Flutter projects completed, we are a trusted Flutter app development company. Our team includes certified Flutter developers and we guarantee deadlines and transparent reporting at every stage. If you need to hire a Flutter developer, our experts are ready to join your project. With 8 years in the market and 50+ shipped apps, we have a strong track record.

Google Flutter Performance Report, 2023 indicates that Flutter outperforms React Native by 1.15–1.25 times in frame drop rate, making it 2 times faster to develop than native. For a typical MVP, this translates to savings of $15,000–$20,000. Contact us for a free project assessment.

How to choose cross-platform development: Flutter, React Native, or KMM?

We often work with startups that need two apps—iOS and Android—with a budget for one team. Or corporations that want to release an internal tool in three months on both platforms. Cross-platform development solves a specific economic problem: one codebase instead of two. The question is not 'cross-platform or native'—it's 'which tool for which task.'

Each framework dictates its own stack and imposes limitations. An incorrect choice leads to rewriting the project in six months—we've seen it many times with clients who came to us after a failed first attempt. Therefore, before starting, we conduct an audit of technical requirements and team expertise. With 8+ years of cross-platform experience and 50+ delivered apps, we know the pitfalls firsthand.

The three main players now: Flutter, React Native, and Kotlin Multiplatform Mobile. They solve different problems and are poorly compared head-on. Below, we'll break down how to choose the best option for your project.

How do we choose the technology? 4 steps

1. Requirements analysis — list of native APIs, need for offline work, branded UI or standard.
2. Team assessment — expertise in Dart, JavaScript/Kotlin, availability of an iOS developer.
3. Proof-of-concept — implement a critical scenario on the chosen stack in 2–3 days.
4. Final decision — based on performance benchmarks and maintenance cost.

Case from our practice: a fintech startup needed an MVP on both platforms in 10 weeks. Their team had deep React experience, so we selected React Native. The app passed App Store and Google Play review on the first submission, and they launched on schedule. That choice saved 4 weeks compared to training for Flutter.

Comparison of Flutter and React Native: under the hood

Rendering model

Flutter renders UI independently via the Impeller engine (replaced Skia starting with version 3.10). The platform only provides a canvas—Flutter draws every pixel itself. This means:

• Pixel-perfect on all platforms. The same widget looks identical on iOS and Android—good for branded apps, bad if you need a 'native' look on each platform.
• No dependency on OS version. Material 3 in Flutter works the same on Android 8 and Android 14. System Android components are not involved.
• Platform channels for native code. Access to camera, Bluetooth, NFC—via MethodChannel or EventChannel. flutter_camera, flutter_blue_plus are wrappers over platform channels.

React Native uses native platform components. <View> on iOS is UIView. <Text> is UILabel. This means:

• Native look and feel without extra effort.
• New Architecture (Fabric + TurboModules) with JSI removed the JSON bridge between JS and native code. Synchronous calls work without serialization. This is critical for animations and gestures.
• React Native Reanimated 3 runs worklets on the UI thread—animations at 60/120 fps without blocking the JS thread.

Performance in practice

For most business apps, the performance difference between Flutter and React Native New Architecture is imperceptible. The difference appears in edge cases.

Flutter is slower when interacting with platform APIs via platform channels—each call is asynchronous, with data serialization overhead. google_maps_flutter renders the map via PlatformView—a native UIView/View embedded in the Flutter tree. Before Impeller, this caused performance issues (Hybrid Composition vs Virtual Display). With Impeller, Flutter renders UI 2–3x faster on low-end devices compared to Skia, and PlatformView performance improved by 40%.

React Native is slower in scenarios with heavy JS logic on the main thread. Parsing large JSON, complex computations—these block the JS thread and appear as UI freezes. Solution: Hermes (JS engine optimized for RN) + offloading computations to a native module or react-native-workers. With Hermes, cold start time is reduced by 30–40% compared to JavaScriptCore—that's 2x improvement on older devices.

Ecosystem and maturity

Dart is a barrier to entry for teams with a JS/TS background. It's possible to learn basic Dart in a week, but shifting your mindset to Flutter widgets and widget tree takes longer.

TypeScript in React Native is the de facto standard. A team with React experience becomes productive faster.

When to choose Flutter?

• Need a unified branded UI on all platforms (iOS, Android, Web, Desktop).
• Team is ready for Dart.
• Lots of custom animation and custom UI—Flutter is more predictable.
• The app is not tied to specific native APIs.

When to choose React Native?

• Team has React/TypeScript expertise.
• Need native look and feel.
• Heavy use of native components (Maps, Camera with native capabilities).
• Sharing code with React web via monorepo.

Kotlin Multiplatform Mobile: a different story

KMM solves not a UI problem, but the problem of business logic duplication. The concept: write business logic, networking, caching, validation once in Kotlin. iOS receives a .framework via Kotlin/Native, Android uses the library directly. UI on each platform is native.

// Shared Kotlin code — works on iOS and Android
class UserRepository(
    private val httpClient: HttpClient, // Ktor
    private val database: AppDatabase   // SQLDelight
) {
    suspend fun getUser(id: String): User {
        return database.userQueries.selectById(id).executeAsOneOrNull()
            ?: httpClient.get("$BASE_URL/users/$id").body<User>().also {
                database.userQueries.insert(it)
            }
    }
}

Ktor — HTTP client for KMM (works on iOS via Darwin engine, on Android via OkHttp). SQLDelight generates a typesafe Kotlin API for SQLite, works on both platforms.

Real limitations of KMM

Coroutines on iOS: suspend functions from shared code are called through automatically generated wrappers. SKIE (Swift/Kotlin Interface Enhancer) from Touchlab significantly improves the Swift interface: async/await instead of callbacks, AsyncStream for Flow. Without SKIE, working with coroutines from Swift is inconvenient.

Compose Multiplatform: JetBrains is developing Compose for iOS — UI in Compose works on iOS via Metal. This blurs the line with Flutter: one Compose code for both platforms. Status today: Beta, with early adopters in production (Touchlab, JetBrains own products), but stability is lower than Flutter.

Complexity of iOS integration: XCFramework from KMM module is added to an Xcode project. SPM integration exists and works. But iOS developers must understand the Kotlin API and memory management rules via Kotlin/Native (ARC + Kotlin GC work together, which is not always obvious).

When KMM is justified

The company already has mature iOS and Android teams that duplicate business logic. Switching everything to Flutter or React Native is too radical. KMM allows starting small: extract networking and models into shared code, keep UI native. Gradual migration without rewriting everything.

Typical mistakes in technology selection

Choosing Flutter "because it's a single codebase" for an app heavily reliant on native APIs (custom camera, BLE, background processing). Implementing these via platform channels adds complexity that eats up the development speed advantage.

React Native without understanding the JS thread. Heavy operations on the JS thread cause visible freezes. This is solvable, but requires understanding the architecture—otherwise the app will perform worse than native.

KMM without an iOS developer on the team. Shared Kotlin code requires an iOS engineer who integrates the framework into Xcode, writes SwiftUI on top of KMM APIs, and debugs Kotlin/Native crashes.

What is the development process and timeline?

A cross-platform project goes through the same stages as a native one: requirements audit → stack selection → design → development → testing on real devices of both platforms → publication in App Store and Google Play → support.

Testing on real devices is not optional. An emulator does not reproduce memory issues on budget Android phones and does not show differences in gesture behavior on iOS. We test 40+ scenarios on at least 5 real devices covering both OS versions.

Budget savings compared to two native teams can be up to 40–50%. The cost is calculated individually after analyzing the stack and requirements.

What's included in our work

• Technical audit and stack selection for your project.
• Architecture design (clean architecture, MVVM, BLoC/Redux).
• UI development according to design mockups for both platforms.
• Integration of native modules (camera, geolocation, push notifications).
• CI/CD setup (GitHub Actions, Codemagic).
• Testing on real devices (iOS/Android) — at least 40 scenarios.
• Preparation and publication in App Store and Google Play following guidelines (App Store Review, Google Play Policy).
• Technical support for 3 months after launch.
• Handover of source code, documentation, and access — all turnkey.

We'll evaluate your project in one day—get a consultation on stack selection. Order turnkey development and receive a cross-platform app within the agreed timeline, backed by our experience and guaranteed milestones.