Flutter, one language, five targets.

Three signals favor Flutter. One, you need to ship beyond mobile (web, desktop, embedded) and want one codebase across all of them. Two, you want pixel-identical UI across iOS and Android because Flutter draws every pixel itself via its own renderer rather than relying on native widget translations. Three, your team has or prefers Dart, or they come from a strong object-oriented background where Dart's type system fits. Three signals favor React Native. One, your team is deeply React and TypeScript already. Two, the app is mobile-only and OTA update velocity matters. Three, the ecosystem of JavaScript libraries matters more than the Flutter widget library. Neither is wrong; they are two excellent frameworks for different team shapes.

US and UK senior Flutter engineers are $135 to $190 per hour; Indian senior engineers are $80 to $130 per hour. A Flutter MVP with Material 3 + Cupertino UI, 15 to 25 screens, auth, push, and store submission runs 10 to 16 weeks. A full production build with platform channels, offline sync, IAP, and custom CI/CD runs 14 to 22 weeks. A multi-platform build targeting mobile + web + desktop runs 16 to 26 weeks. A 2-week audit is refundable. Scoped quote in 48 hours.

For internal tools, dashboards, and progressive web apps shared with mobile, yes. Flutter Web via CanvasKit renderer gives pixel-identical UI to mobile, which is useful when the experience needs to match. For public content-heavy web sites (SEO-critical, large-first-load-sensitive), Flutter Web is rarely the right choice; the initial bundle is large and SEO support is limited. Our rule: Flutter Web is right when the web target is an internal or authenticated experience; wrong when it is a public marketing or content surface.

Riverpod for most new builds. It is the successor to Provider by the same author, with stronger type safety, testable providers, and compile-time dependency resolution. BLoC for teams that prefer explicit event-driven architecture, common in large enterprise apps. Provider for smaller apps or teams migrating from older Flutter codebases where Provider is already in use. We avoid GetX for production builds. The right default for a new Flutter project in 2026 is Riverpod plus freezed for immutable data classes.

Platform channels. Flutter's MethodChannel and EventChannel let Dart code call Swift or Kotlin methods on each platform. For common needs (camera, location, push, biometrics), we use maintained pub.dev packages that wrap the native APIs. For truly custom needs we write a Flutter plugin: Swift code for iOS, Kotlin for Android, exposed to Dart through a channel. The plugin lives in a separate package for reusability. Most Flutter apps need 2 to 5 custom native integrations, all wrapped in plugins.

Usually not. The pragmatic pattern: Material 3 as the primary design system for Android with dynamic color and modern Material UI affordances. Cupertino widgets used on iOS for native-feeling navigation bars, action sheets, and sliders where platform expectation matters. Most of the app (buttons, inputs, layout) uses a shared design system that works on both. We build a design system on top of Material 3 with brand tokens, then override with Cupertino equivalents only where the iOS user expectation would be broken otherwise.

Three options. Codemagic for Flutter-native CI/CD with first-class support for iOS and Android builds, App Store and Play Store submission, and Flutter-specific test running. Fastlane with GitHub Actions or GitLab CI for teams already on those platforms, with the fastlane-plugin-flutter gem. Bitrise for teams needing a mobile-specific but more configurable pipeline. We pick based on the team's existing CI/CD surface; all three work. Signed builds happen in CI; no manual Xcode exports in 2026.

You do. Private GitHub repository under your organization. Apple Developer Program and Google Play Developer Console under your legal entity. Signing certificates in your keychain and keystore (we keep encrypted backups for CI but you own the originals). Push notification providers, analytics, crash reporting all under your billing. DH engineers are named collaborators, removable any time. On exit: repository transferred, credentials rotated, documentation handed off, 30-day support tail.