Direct answer — What is the right way to shut down (sunset) a live mobile game without losing player trust? The right way to sunset a mobile game is to decide the refund, virtual currency, data and support plan before you announce anything, then give players a long, clearly dated wind-down: stop selling on announcement day, let players use what they already bought until shutdown, and tell them through every channel what will stop working and when. Documented cases sit around three months of notice (96 days for Kim Kardashian: Hollywood, about 16 weeks for Google Stadia). Treat the final weeks as a farewell event, not a silent switch-off, because players and the press judge the studio on how its last game ended.
Knowing how to sunset a mobile game has become a core leadership skill in 2026. Portfolios are being cut, live teams are being merged and studios are making hard calls on titles that still have loyal, paying players. Shutting down a live service game is rarely a failure of the people running it; doing it badly, though, is a reputational failure the studio carries into its next launch.
I have spent more than 20 years at Gameloft, SFR, Blacknut and Impulse Media Hub, with more than EUR12M of P&L under my responsibility, and I have operated live services long enough to see how the way a service ends shapes the reputation of the team behind it. When studio leaders bring a sunset decision into a mobile game consulting engagement, the question is rarely “should we close?” anymore. It is “how do we close this title so that players, platforms and partners still want to work with us afterwards?”
Why live service game end of life is a 2026 leadership issue
A game sunset is the planned end of a live game’s service: sales stop, servers shut down and the app is removed from stores, in a sequence announced to players. In a live service game, the product is the service. When the service ends, everything players paid for inside it ends too, which is why game shutdown player communication carries so much more weight than a normal product retirement.
Three forces make live service game end of life a board-level topic this year:
- Portfolio pressure. The market reset I described in my analysis of the 2026 mobile game strategy reset forces studios to concentrate budget on fewer titles. Sunsets are the other side of that concentration.
- Regulatory attention. The Stop Destroying Videogames citizens’ initiative collected 1,294,188 verified statements of support. In its 16 June 2026 reply, the European Commission concluded that “at this stage it cannot propose a legal obligation to keep video games playable after they stop being provided commercially”, but it committed to start an exchange with industry and consumer representatives by end 2026 “to draw up an industry code of conduct on managing video games’ ‘end of life’.”
- Reputation compounding. Players remember how a studio treated their purchases. That memory resurfaces in reviews, community forums and press coverage the day your next game launches.
The two reference cases: Kim Kardashian: Hollywood and Stadia
Two well-documented sunsets, analysed by the law firm Frankfurt Kurnit Klein & Selz, give a practical benchmark for what “doing it properly” looks like.
| Element | Kim Kardashian: Hollywood (Glu, 2024) | Google Stadia (2022-2023) |
|---|---|---|
| Announcement | 3 January 2024, via community forum and in-game countdown message | 29 September 2022 |
| End of service | Players could keep playing until 8 April 2024 | Shut down at 11:59pm PT on 18 January 2023 |
| Notice period | 96 days from sunset notice to shutdown | About 16 weeks |
| Purchases | In-app purchases discontinued; existing in-game currency usable until shutdown | New purchases turned off; refunds for hardware bought through the Google Store and for game and add-on content bought through the Stadia store |
| Player data | Instructions for saving the player’s Hollywood ID | The analysis recommends explaining data access and saving during the wind-down |
| Farewell | Engagement options for the final days recommended in the analysis | Google released an internal game as a farewell for players |
The two cases differ on refunds, and that difference matters. Stadia was a platform with hardware and full-price games; a free-to-play mobile title funded by microtransactions over years faces a different economic and legal situation. What both cases share is the structure: early notice, sales stopped first, purchased content usable until the end, clear data instructions and a support plan sized for the surge.
How to sunset a mobile game: the GGA wind-down timeline
The timeline below is my own operator method, built from the reference cases above and from my experience. It is not an industry standard, and the exact durations must be validated against your platform terms, contracts and legal advice in each market.
| Phase | Timing (GGA method) | What happens |
|---|---|---|
| Internal decision | Before any announcement | Final go/no-go, refund and currency policy, data plan, partner and platform notifications, support staffing |
| Announcement day (T0) | Day 0 | Public notice on every channel, in-app purchases switched off, subscriptions cancelled or set to lapse, FAQ live |
| Wind-down | From T0 to the final weeks | Purchased content and currency remain usable, regular reminders, community managers active |
| Farewell | Final weeks | Content unlocked, currency gifted, farewell event, data export or account instructions repeated |
| Shutdown | Announced date | Servers off, store listing removed, final message to players |
| After shutdown | Following weeks | Support desk open for refund and data requests, post-mortem for the team |
For a title with active paying players, I plan for roughly three months between announcement and shutdown, in line with the 96 days and about 16 weeks of the two documented cases. Shorter windows are sometimes forced by cash, but they should be a conscious decision, not the default.
Facing a sunset decision on one of your titles? Book a Strategy Call and we will stress-test the timeline, the refund policy and the player message before anything goes public.
Refunds, virtual currency and player data
This is where most reputational damage happens, and where a mobile game refund policy shutdown plan must be decided before T0, not improvised after the first angry forum thread.
Stop selling on day one
The single most important rule: the moment you announce the sunset, stop taking money. Glu discontinued in-app purchases and Google turned off new purchases at announcement. Selling currency that players know they cannot spend for long is, in my view, indefensible, and it invites exactly the consumer claims and regulator attention a sunsetting plan is meant to reduce.
Subscriptions need specific attention. Glu told players to cancel platform-managed subscriptions, and the FKKS analysis recommends turning off subscriptions to limit new purchases. Check every recurring product: VIP passes, battle passes and season passes.
Let players use what they paid for
The standard set by Glu is that “existing in-game currency can still be used” until shutdown. For a free-to-play game, the practical options are:
- Use until shutdown (the Glu model): currency and purchased items stay usable until the last day.
- Proactive refunds (the Stadia model): purchases are refunded without players having to ask. This is the strongest trust signal and the most expensive.
- Hybrid: refunds for recent purchases, use-until-shutdown for older ones.
The right option depends on your revenue history, your store terms and your markets. This is not legal advice: consumer protection rules differ by jurisdiction, and refund handling through Apple and Google follows their own processes. Involve counsel early, and prepare the support team for refund requests whatever you decide.
Tell players what happens to their data
Players want to know two things: what happens to their progress, and what happens to their personal data. Explain whether an account, ID or progress can be saved or exported, and when personal data will be deleted. The FKKS analysis recommends to “coordinate with privacy and development teams so that player data is handled in compliance with privacy requirements.” My gaming regulation and compliance guide covers the wider privacy obligations mobile studios already carry.
Game shutdown player communication: channels and message
Players should never discover a shutdown through a failed login. Use every channel you have, and repeat the message.
- In-game: a persistent notice with the shutdown date, ideally a countdown, as Glu did.
- Community: forum post, Discord, social accounts, with community managers available to answer.
- Store listing: an updated description once sales stop.
- Support: a dedicated FAQ and a support team sized for the surge.
Be precise about the store mechanics. Google’s Play Console Help states that when you unpublish an app, “new users won’t find and download it on Google Play,” while “existing users can still use your app and receive app updates.” Unpublishing is not the end of service: for a server-based game, the server shutdown is. Players need both dates, and an explanation of what stops working at each one.
The message itself should be short and human: why the game is closing, the exact dates, what happens to purchases and data, and a genuine thank you. Avoid corporate language about “strategic realignment”. Players accept a business decision; they do not accept being treated as a line item.
Game studio reputation management at shutdown
Game studio reputation management during a shutdown is mostly about the last weeks. The FKKS analysis suggests unlocking existing content, gifting currency or adding free content so players get a good ending; Google released a farewell game for Stadia players. In my experience, the farewell is what players remember and screenshot.
Three practices protect the studio beyond the title:
- Brief partners before players. Platform account managers, advertising partners, licensors and any publisher need to hear it from you first. A partner who learns of a shutdown from the press is a partner you lose.
- Protect the team’s story. A sunset often comes with restructuring. If the studio is also rethinking its model, the options in my studio survival strategy guide apply directly.
- Write the post-mortem. What the live data told you, when, and what you would do differently. This is the asset you carry into the next game, and into your LiveOps strategy for the titles you keep.
What we could not verify
I could not verify a universal legal minimum notice period for mobile game shutdowns: rules depend on jurisdiction, contract terms and the type of product, so none is stated here. I did not find official Apple documentation, retrievable at the time of writing, describing what happens to existing users and in-app purchases when an app is removed from the App Store, so the store mechanics above cite Google Play only. I also found no reliable dataset on how sunsets affect a studio’s next launch; the reputational points reflect my own practice. The timeline durations are the GGA operating method, anchored on two documented cases, not a market benchmark.
Conclusion
Shutting down a live service game well comes down to sequence: decide refunds, currency and data first; stop selling on announcement day; give players a long, dated wind-down; and end with a farewell rather than an error screen. The studios that do this keep their reputation intact for the next launch. The ones that skip steps pay for it in reviews, partner trust and press coverage.
Planning the end of a live title? Talk to Game Growth Advisor about a sunset plan that protects your players, your partners and your next game.