A case study in white labeling apps
summary
A configuration-driven Flutter Web system is built to run many client-branded apps from one monorepo using AWS and GitHub Actions with Dart defines for host and API key; it ships configurable form elements (typed enums, metadata, include/default/persist functions), a page/section validator, and testable value-keyed widgets for integration tests. Runtime JSON-driven theming fails today because lambdas break serialization, so the app mostly works for rapid client setup but still needs a lambda-free function registry to achieve fully remote white‑labeling.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 2:51Customizing build process
- 6:16Configuring UI elements
- 9:25Building configurable forms
- 15:02Handling state and validation
- 22:49Page navigation and routing
- 28:30Form validation logic
- 33:47Testing and debugging
- 35:53Achieving dynamic configuration
- 37:16Q&A and closing remarks
related talks
42mWhite-Label Architecture in Flutter: Drowning in Abstractions
40mWhite labelling apps - a year later
44mHow We Built the Superapp "Dealer Online" and What Came of It
35mMaking the Jump from Design to Product
42mDark patterns and Mobile UX Design
30mSuperstar Session: Publishing Isn’t ‘One Size Fits All’ - What Does Your Game Need?
30mA PLN 2M App - Taxi5 Case Study
37mLessons learned from crafting an in-house framework