Summary
Games as a Service (GaaS) is a design and business model in which a game is treated as an ongoing service rather than as a finished boxed product. The focus shifts from a one-time sale to long-term retention, regular updates, social stickiness, and sustainable monetisation. In Clark’s treatment, this is not just a publishing model but a design condition: the game’s loops, economy, session structure, and social systems all need to support repeated return over time. (Clark, Games as a Service, see source-games-as-a-service)
Key ideas
- the product is ongoing rather than finished at launch
- retention matters as much as acquisition
- live economies, content cadence, and social systems become central design concerns
- monetisation must be integrated into the experience rather than bolted on afterwards
In practice
For a student project, GaaS thinking usually means planning:
- a repeatable core loop
- a reason to return tomorrow, not just to continue right now
- a sustainable internal-economy
- clear live priorities for updates, analytics, and player communication
Evidence
Clark frames service games around long-term player relationships, lifecycle thinking, and the need to design for return, not just first-session fun. The same source also stresses that engagement, monetisation, and social design cannot be treated as separate systems. (Clark, Games as a Service, see source-games-as-a-service)
Implications
Treating a game as a service changes the design question from “is this fun now?” to “why would a player stay, return, and spend time here over weeks or months?”
Open questions
- Which kinds of student projects genuinely benefit from service-game thinking rather than a finite premium-game structure?
- At what point does a service design model become too operationally expensive for a small team?