Cross-Platform Game Development: 10 Lessons from Mobile to PC & Console
GDC Festival of Gaming details Ian Fielding’s talk on how Super Evil Megacorp evolved from a mobile-first studio into a cross-platform developer, using TMNT: Splintered Fate as the case study. The focus is on the practical lessons behind shipping the same game on PC, Switch, PlayStation, and Xbox without losing the design or production advantages of the original build.
For developers, the useful part is the transition itself: moving from touch-first assumptions to controller and keyboard/mouse support, while also dealing with platform-specific performance targets, UI scaling, and the realities of console certification. That kind of expansion tends to expose every hidden dependency in input, rendering, save systems, and build pipelines.
The talk is also a reminder that “cross-platform” is less a feature than a production strategy. Teams that start mobile-first can still reach premium platforms, but only if they plan for abstraction, content parity, and enough engineering headroom to avoid one platform dictating the whole architecture.
GDC says the session is part of its broader programming, audio, art, business, and production coverage, with the next conference scheduled for March 1-5, 2027 in San Francisco. For studios weighing a mobile-to-PC/console expansion, the main takeaway is that the technical and production costs are real, but so is the upside if the foundation is built to survive the jump.
- what
- Ian Fielding shares 10 lessons from moving Super Evil Megacorp from mobile-first development to cross-platform shipping.
- who
- Super Evil Megacorp; Ian Fielding, CEO; TMNT: Splintered Fate.
- when
- GDC says its next conference runs March 1-5, 2027, in San Francisco.
- impact
- Relevant to teams planning mobile-to-PC/console ports, especially around input, UI, performance, and certification.
Useful guidance, but cross-platform expansion is costly and complex.
Follow Nintendo Switch updates
See relevant stories in your personalized news feed.
Discussion