Write once, ship multiple times
summary
Claim: a maintainable whitelabel product exists and works if most business logic lives server‑side and apps share only configurable UI and feature boundaries. Concrete tools and patterns used: Gradle product flavors, MVP presenters, Dagger for injection, Retrofit/OkHttp, feature packages, Firebase Remote Config, and optional image libraries like Glide or Picasso swapped via use interfaces + DI. Real scale examples appear (tens to hundreds of apps, a 15‑app sudden fork), common failures include fat clients and hard‑coded logic so the recommended rule is move business logic to server.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:36What is White Label System
- 8:42System Architecture
- 14:58Constants
- 16:08Gradle
- 16:57Configuration
- 20:10Interfaces
- 23:39Features
- 25:28Examples
- 28:12Example
- 31:31White label system
- 35:11Summary
related talks
41mWrite once, ship multiple times
17mBest Practises for Android Development as a Daily Business
41mIt Just Works
30mJourney of the Android white label process
27mModularising the right way
27mHalf Way to clean architecture
40mClean, Easy & Stable Android Architecture
29mDon't reinvent the wheel, use libraries: Modern Android Stack