Game as a service
Evgeny Shegal
What the talk is about
Evgeny Shegal explains how to build the meta-game for free-to-play projects with a loot-box economy that run for years as a service. The core challenge is keeping code quality high over a long life: code keeps growing, the engine and IDE get upgraded, and a release is needed every 1–3 months. The team's principles are never sacrificing quality, testability, availability, the ability to switch features off live, good performance on weak hardware, and observability through statistics. Practices include agile, non-functional requirements, planning sessions, cross-functional teams, technical designs, feature documentation, a tester working next to developers, code review and automated tests. He closes with a Swagger/OpenAPI example that let the team auto-generate client protocol code. Useful for developers and leads of live games.