Production Fluttering
summary
Built Jimdo Boost with Flutter in roughly three months, runs in production for 3+ months and shares one codebase across Android and iOS; tooling includes Dart, a custom Swagger codegen (to avoid mirrors), TravisCI + fastlane, Sentry for crashes, and flutter_wrapper to pin SDKs. Hot reload yields fast dev cycles and native‑smooth UI, localization tooling and crash capture require extra work (use error zones), and there is no background Dart execution, limiting push notification handling; app ships, works well, with minor teething bugs. hot reload compiled AOT to ARM
AI-written summary · about
chapters (12)
- 0:00Introduction and background
- 3:14Why we chose Flutter
- 7:10Flutter’s Dart language
- 11:16Building Jimdo Boost with Flutter
- 13:03Approach to REST APIs
- 17:05Flutter versioning and tooling
- 20:59Crash reporting in Flutter
- 23:51Handling background execution
- 26:43CI, testing and localization
- 28:50System integrations and performance
- 30:57Flutter vs native development
- 32:03Q&A
