Kabam abandons Windows Phone development after releasing just one game
Windows Central has learned that Kabam, one of the biggest mobile game developers, has decided to stop making titles from the Windows Phone platform. This decision represents a complete reversal of Kabam's original plans …
Context & Ripple Effects
Kabam's exit lands on a platform already bleeding developers: weeks earlier Softcard had shut down its Android and Windows Phone apps following the Google deal, and Good Technology data shows Windows Phone stuck at roughly 1% of global enterprise activations through late 2014 and into Q1 2015. For a studio of Kabam's scale — a top mobile publisher that had been acquiring studios like Phoenix Age to feed its portfolio — the economics of supporting a single-digit-share platform were the point of the reversal.
The decision is also a leading indicator rather than an endpoint: three months later Microsoft itself dramatically scaled back its Windows Phone ambitions, leaving Lumia's long-term future in doubt, and the platform's developer exodus only accelerated from there.
First-order effects
- Windows Phone users lose access to future titles from one of mobile's biggest publishers immediately after getting just one game, deepening an app gap the platform could not afford.
- Kabam reallocates development resources away from a ~1%-share platform toward iOS and Android, where its acquisition-fed catalog actually monetizes.
Second-order effects
- Every remaining third-party developer now has fresh evidence that even flagship publishers judge Windows Phone not worth the porting cost, making each subsequent abandonment easier to justify — Softcard's departure and Kabam's form a visible pattern.
- Microsoft is pushed toward bridging the gap with tooling instead of native commitment, a path it pursued via Android-app porting efforts before canceling Project Astoria the following year.
Third-order effects
- The sequence — developers leave, share stagnates, first-party support recedes (Windows Phone 8.1 support ended in 2017), and even Microsoft's own mobile apps stop gaining features by 2018 — traces the full arc of a mobile platform unwinding into irrelevance despite its maker's resources.
The trend: Mobile platforms below critical developer mass enter a self-reinforcing exit spiral: each high-profile abandonment like Kabam's raises the perceived risk for the next developer deciding where to ship.