Lessons Learned from Launching a Flutter app in Production
summary
A Flutter app named fluttips.dev fetches raw Markdown from a GitHub repo and does client-side preprocessing, rendering via flutter_markdown, and offline caching with Drift/SQLite and cache_network_image (7‑day expiry). A GitHub personal access token is hardcoded, rotated yearly and gated by a Firebase Remote Config force‑upgrade. Errors go to Sentry, analytics to Mixpanel/Firebase. Launch yields 2.4k downloads, ~100 daily active users, ~80 reviews, and only 0.27% of site traffic from the app; overall the app ships quickly and works, with some store rejection for icon trademark.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 4:22App concept and demo
- 8:14Technical architecture
- 15:21GitHub API limitations
- 18:28Pre-launch testing
- 26:32Launch strategy
- 30:24Post-launch issues
- 32:55Lessons learned
- 35:44Q&A
related talks
41mThe Flutter journey from a Personal App to a Successful Production App
34mProduction Fluttering
41mThe Flutter Journey to a Production App
40mMy Experience Building DevCommunity.org in Flutter
28mFlutter App Implementation Seen in Code
49mFlutter In Practice – Tips and tricks for writing Flutter apps, from Start to Finish
38mFlutter: A Path of Vines and Flowers
21mOffline first Flutter applications