F&B · multi-brand
White-label ordering & loyalty
One modular codebase where each brand is theme tokens, feature flags, menus, and loyalty rules — not a separate app fork.
KotlinJetpack ComposeServer-driven UIGraphQL
Config
over forks
The problem
Chains that grow brand-by-brand often end up with drifted forks: every menu or loyalty change means multiple releases and divergent bugs.
What we did
- 01Collapse forks into a shared modular app with per-brand configuration bundles
- 02Server-driven UI so merchandising and campaigns ship without a store release
- 03Shared ordering — pickup, delivery, scheduling — with brand feature flags
- 04Per-brand CI signing and staged rollouts from one pipeline
Outcome
- New brand launches become configuration, not a rewrite
- Faster cold-start and screen loads after shared image and SDUI work
- One architecture your team can maintain across the portfolio