White labelling apps - a year later
summary
A production Flutter app moves all UI and behavior into remote JSON configs using JSON Serializable, enhanced enums for function types, a factory that instantiates typed data elements, and a mustache-style injector; deployments become simpler and the app is now fully configurable, though some configs reach 3,434 lines and debugging is harder. Assets use remote URLs with optional blurhash and ratios, CI/CD pins config structure versions, and launch speed improves by calling runApp twice (loading UI then real app).
AI-written summary · about
chapters (23)
- 0:00White labeling apps intro
- 1:50Last year's config recap
- 6:43Refinance app live demo
- 8:29Customizable app parts
- 11:38JSON serialization choice
- 12:20Flutter serialization challenges
- 14:03Serializing colors
- 15:05Configurable typography
- 17:33Asset handling limits
- 18:37Image management
- 20:23Dynamic string injection
- 22:28Data config evolution
- 26:21Lambdas to enums
- 27:43JSON config structure
- 29:50Debugging large JSON
- 31:13Debugging serialized configs
- 32:36Loading speed strategies
- 34:27Tracking JSON changes
- 35:10Config versioning
- 36:32Tooling next steps
- 37:55A/B testing configs
- 38:57Golden tests
- 39:18Q&A
related talks
42mWhite-Label Architecture in Flutter: Drowning in Abstractions
34mProduction Fluttering
28mFlutter App Implementation Seen in Code
37mFlutter: Mobile Development for Busy People
36mFlutter Add-to-App: The Good, the Bad and the Ugly
38mFlutter: A Path of Vines and Flowers
37mFlutter: In Real Life For Real People
41mThe Flutter journey from a Personal App to a Successful Production App