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:
| Approach | Performance | Complexity | Testability |
|---|---|---|---|
| Riverpod 2.x | High | Medium | High |
| BLoC | High | High | High |
| Provider | Medium | Low | Medium |
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
- Requirement analysis and technical specification (1–2 days)
- UI prototype and architecture design (1–2 weeks)
- Business logic and API integration (core sprint)
- Native plugin development (if needed)
- CI/CD setup via GitHub Actions
- App store submission support
- Post-release support (2 months)
Common Mistakes in Self-Development
We most often see three problems when auditing Flutter projects from other teams.
-
Incorrect provider architecture.
ChangeNotifierwith global state that rebuilds the entire screen on any change. Switching toRiverpodwith granularselectcalls solves the problem but requires refactoring. -
Platform channel without error handling. Native code throws an exception → the channel fails → the app crashes without a clear message. We wrap all
MethodChannelcalls intry/catch PlatformException. -
Ignoring isolates for heavy operations. JSON deserialization of a 10MB response on the main isolate causes noticeable freezes.
compute()or manualIsolate.spawnis mandatory for data >1MB.
Timelines
| Project Scale | Approximate Timeframe |
|---|---|
| MVP, 5–10 screens, REST API | 6–10 weeks |
| Mid-sized product, 15–30 screens, offline mode | 3–6 months |
| Complex product: real-time, payments, maps, BLE | 6–12 months |
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.