In most live games, every layer of the player experience ships through the same process: build, QA, cert, deploy. That makes sense for core gameplay. It doesn't make sense for your shop, your seasonal events, or your patch notes.
The result: seasonal content gets locked in weeks early. A/B testing a shop layout becomes an engineering project. A text typo costs your players a multi-gigabyte download. And your senior engine engineers spend their time tweaking fonts instead of building the game.
Meanwhile, the other games your players spend time in are refreshing their shops every few days. Different layouts. Personalized offers. Seasonal themes that actually feel seasonal.
The biggest live games solved this by splitting their pipeline in two. Core gameplay stays native, stable, locked down. Everything volatile (the shop, events, community features, compliance content) moves to a web-based layer that deploys independently from the game client.
