It would be easier, organizationally, to run software, mobile, and digital assets as three separate teams with three separate codebases. We deliberately do not. Every client build gets scoped against systems we already run for Romeo, so a fix or an improvement in one place tends to improve everything else.
The cost is that any one engagement has to fit inside a shared set of conventions rather than being a totally bespoke stack. In exchange, a mobile app we ship next quarter starts from a more mature foundation than the one we shipped this quarter — the whole studio compounds instead of each project starting from zero.
It also means one small team can plausibly stand behind everything on the full catalog page, because none of it is a black box maintained by a contractor who has since moved on.
More on the specific stack choices in a future post.