This post is from a suggested group
I've been wrestling with this for months now while maintaining our slot game platform that's been running for over four years. What approaches have you seen for organizing complex code structures in long-lived mobile game hubs without losing developer velocity? Early on we just piled everything into bigger services thinking it'd scale, but refactoring became a nightmare and new features slowed to a crawl. Last sprint we spent three days just untangling dependencies before adding a simple leaderboard. Feels like there's gotta be smarter ways to keep things modular yet fast-moving without burning everyone out on tech debt. Would love real examples from folks who've been through it.

Some projects I worked on leaned heavily into clean separation between core game logic and the surrounding systems, especially when the player base grew. For me the sweet spot came from combining feature flags with smaller, focused modules that could evolve independently. That helped us avoid the usual slowdowns in big hubs. Interestingly enough I stumbled on a solid piece about backend setups for these kinds of apps at https://structurespy.com/inside-a-mobile-game-hub-how-structured-app-design-keeps-complex-game-libraries-usable/ and it matched a lot of the pain points we've hit. Still, no perfect answer exists because every team ends up tweaking things their own way based on what breaks first.