Why I Built an Open-Source Alternative to Shorebird for Flutter Android

Shorebird is a great product. If it fits your team's needs, you should probably just use it. This post is for the cases where it doesn't. The Problem Flutter doesn't officially support hot updates. When a bug ships to production on Android, the only path is to rebuild, re-sign, re-submit, and wait for store review. For teams shipping to multiple Android stores — especially in markets where store review can take days — this is a real operational cost. Shorebird is currently the most mature solution to this problem. But it makes a few choices that aren't universal: The backend is closed-source. Patch metadata, user telemetry, and rollout state all go through Shorebird's infrastructure. It's a paid service, priced per patch install on the team tier and above. The CDN's primary edges are in the US and EU. For users in Asia, patch fetch latency varies. Your production runtime depends on a third-party service staying available long-term. For some teams these are fine tr