The situation
Restaurant groups needed rewards apps on iOS and Android that guests would recognise as that restaurant, without standing up a separate engineering programme for every brand.
The constraint
Each store listing has to stand as that restaurant app. Rewards behaviour underneath has to stay consistent, or every brand becomes a fork. The record does not say who owned each store account, or which public listings were in scope.
How the team was shaped
The record does not name a team shape. A similar programme would be staffed with mobile and backend engineers you interview and approve, working in your repositories. This note does not describe a headcount.
What had to stay true after launch
| Need | Why it mattered |
|---|---|
| iOS and Android | Guests do not share one store |
| A listing under the restaurant name | A shared vendor brand in the store is a different product |
| Shared rewards behaviour | A fork per brand does not stay in step |
What this note does not claim
It does not name restaurants, publish store links, or count the apps. A list of public store links is not evidence that a national chain app was built here. It does not publish revenue, headcount, or a savings figure.
Working through this in your own GCC plan?
We will give a direct answer on a short call.


