Integrating Shorebird CodePush into Scalable Flutter Architectures
summary
Shows a production integration of Shorebird CodePush into a three-layer clean architecture that isolates SDK code in the Data layer, keeps update rules in Domain, and orchestrates checks and restarts in a Service layer. Claims hotfix time drops from days to minutes, serving ~200,000 merchants with 1–3 MB patches, implements a 10-minute check interval, handles asset/tree-shake pitfalls, offers auto/prompted/silent restart UX strategies, and reports high reliability in production.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 4:16Code push for critical fixes
- 9:21Shorebird CodePush
- 11:34Shorebird's patching process
- 13:45Production code push philosophy
- 16:17Vendor-agnostic domain layer
- 18:21Data layer with Shorebird
- 19:48Service layer orchestration
- 21:39Update flow and error handling
- 24:48App restart UX challenges
- 28:44Silent staging updates
- 30:12Real-world challenges
- 33:46User state during restarts
- 35:13Production cost analysis
- 37:48When to use code push
- 39:15Q&A
related talks
34mShorebird CodePush: Revolutionising Flutter App Updates
15mSpeed Up Your Mobile Patches in Prod with Shorebird & Flutter
34mProduction Fluttering
31mFlutter with 50+ Engineers
29mArchitecting the Reactive App with Flutter
45mFlutter: A journey of productivity and happiness
45mBuilding Products Full-Stack with Dart and Flutter
09mFlutter for Enterprise: How your company should be building with Flutter at scale