Cross-Platform Production: What Nobody Tells You About Shipping on 10+ Platforms
By Craig Wells, Senior Director of Operations, Super Evil Megacorp
Between July 2024 and February 2026, we shipped TMNT: Splintered Fate across every major gaming platform (console, PC, and handheld) in both digital and physical editions, alongside three DLC releases and a brand-new game mode, all while running live operations on the original Apple Arcade version that started it all.
TMNT: Splintered Fate had launched on Apple Arcade in May 2023 and was performing well. When we were able to take it cross-platform, we set an ambitious target: Nintendo Switch by July 2024, PC storefronts by November, and PlayStation and Xbox to follow in the new year. Fifteen-plus SKUs across console and PC, all within roughly a year of starting execution.
What made the schedule particularly daunting wasn’t just the platform count. It was everything running in parallel. We weren’t porting a finished game and calling it done. We were simultaneously running live operations on Apple Arcade, developing and shipping our first major DLC (a new level and playable character driven by community demand, which dropped in February 2025), building an entirely new game mode alongside our second DLC in October, and managing the continuous drumbeat of hotfixes, balance updates, and patches that any live game demands. By late February 2026, we’d shipped three DLC releases alongside the full platform expansion.
That’s the reality of cross-platform production at a mid-size studio: you don’t get to stop the clock while you expand. Every platform launch happens alongside everything else. When studios talk about “going cross-platform,” the conversation usually centers on technical challenges: performance on Switch, input methods, scalable graphics. These are real questions, but they’re also just the start.
The broader question is:
Can we ship 15+ SKUs across console and PC without missing launch windows, disappointing players on specific platforms, or burning through our budget in submission revisions and rushed hotfixes?
Certification processes, storefront optimization, platform-specific player expectations, coordinated marketing: that’s where cross-platform production actually lives.
Here’s what we learned doing it.
That's the reality of cross-platform production at a mid-size studio: you don't get to stop the clock while you expand.
The Reality: A Strategic 2-Year Rollout Across Platforms
Expanding to console and PC was always part of the vision – the question was sequencing it strategically. We were deliberate about the order: Switch first (closest to mobile performance specs), then PC (largest overall market), then PlayStation (larger console market share), then Xbox. Each platform taught us lessons that informed the next.
That’s 15+ SKUs spanning mobile (iOS, tvOS, macOS, visionOS), console (Switch, Switch 2, Xbox One, Xbox Series X|S, PS4, PS5), and PC (Steam, Epic, Humble Bundle, Fanatical, Green Man Gaming, Steam Deck).
Player reception remained consistently strong across every platform we launched on: a 4.7 rating from over 35,000 reviews on the Apple App Store, Very Positive on Steam, positive Metacritic scores on both PC and PS5, 91% on SwitchUp, and 9/10 from CGMagazine. For a mid-size studio managing 15+ SKUs simultaneously, that consistency is the proof point. When your production process is working, quality doesn’t degrade with each new platform; it holds.
Production Truth #1: Submission Timelines Define Your Production Schedule
An easy mistake to make when planning a cross-platform launch is treating submission timelines as a logistics detail rather than a production constraint. They’re not. Submission timelines are your production schedule. For our later platform launches, we were planning 3-5 months ahead of release dates, not as conservative padding, but as the minimum viable runway to coordinate everything that needs to resolve before launch day.
Nintendo’s submission process illustrates why. Their structure is sequential by design: you submit your build for approval first (10 business days), and only after that approval can you create and submit storefront materials (another 10 business days). That’s nearly a month of sequential gates before you can launch, and that’s before accounting for any revision cycles. Understanding that structure early and planning around it rather than against it is what keeps launches on schedule.
Submission timelines are your production schedule.
But certification is only part of the timeline. Marketing asset production runs in parallel, and this is where complexity compounds quickly. For any multi-platform launch you’re managing:
- Localization requirements that vary by region. Storefront descriptions, screenshots with UI text, and metadata each need translation, with some regions requiring specific terminology or cultural adaptations.
- Age rating submissions across multiple systems: PEGI for Europe, ESRB for North America, USK for Germany, CERO for Japan, each with different submission processes, timelines, and costs. Miss one and you can’t launch in that region.
- Regional pricing strategy across dozens of countries, accounting for currency conversions, purchasing power, and competitive positioning.
- Platform-specific asset requirements that compound everything above. Specific screenshot dimensions, trailer formats, and metadata requirements per storefront, with localized versions of each needed per region. Nintendo, for example, requires three versions of every trailer: one with the ESRB rating, one with PEGI, and one without any rating.
In practice, a single platform launch isn’t one timeline. It’s dozens of interconnected timelines that all need to resolve before launch day. Miss one detail (a required screenshot dimension, a pricing approval in one territory, an age rating for a specific SKU) and your coordinated launch slips.
When you’re launching across multiple platforms simultaneously, you’re managing all of this in parallel, each workstream multiplied by the number of regions you’re launching in. To manage this, we front-load rigorous QA testing before submission to catch issues early, and when problems arise we work collaboratively with platform holders to find solutions, whether that’s exceptions for minor issues or committing to fixes in subsequent releases.
A single platform launch isn't one timeline. It's dozens of interconnected timelines that all need to resolve before launch day.
Production Truth #2: Player Expectations Are Platform-Specific (And Critical to Support)
When we launched TMNT:SF on Apple Arcade, our top complaint was lack of controller support.
We had controller support. It worked perfectly. But we hadn’t communicated it clearly in the UI. Players saw touch controls as the default, assumed we’d shipped a mobile-only experience, and left negative reviews. We decided to push a hotfix to make controller support more prominent. It was our first real lesson in what cross-platform production actually demands: getting your game running on a platform is not the same as meeting player expectations for that platform. Understanding what players on each platform consider standard, and delivering it clearly, was institutional knowledge we’d spend the next two years building.
Getting your game running on a platform is not the same as meeting player expectations for that platform.
That early experience shaped how we approached every platform that followed. Each has established norms players treat as baseline requirements, and shipping without them doesn’t just generate complaints. It signals you didn’t take the platform seriously.
A few examples:
- Switch: We knew Switch players would expect couch co-op – it’s one of the platform’s defining features and an obvious expectation for any co-op game on the hardware. We wanted to deliver it at launch, and when Nintendo selected us for launch featuring, that created a hard deadline. What followed was a herculean development effort to accelerate our timeline and ship couch co-op as a day-one feature rather than a post-launch update. It was the right call, and it meant players got the experience they expected from day one.
- Steam Deck: Players expect optimized performance and cloud saves – particularly important because many of our players move fluidly between Steam Deck and Steam, and seamless save progression across both is table stakes for that audience. It represents a significant percentage of our PC playerbase, so we treated it as a first-class platform.
- Apple TV: Expectations were lower, but we exceeded them with 4K support at 60fps, earning goodwill from a small but vocal audience.
Players judge quality not by absolute performance, but by whether you’ve met baseline expectations for their platform. A game that runs identically everywhere but lacks platform-specific features will be dismissed as a rushed port.
This extends to control schemes. We developed three core input paradigms (touch, controller, and mouse & keyboard) and optimized each individually. Players can switch between these schemes on the fly; if a controller isn’t sensitive enough, they can tap the screen and the control scheme switches instantly. On consoles, we focused on controller play and thoughtful button mapping. On PC, we ensured keyboard shortcuts felt natural. That investment paid off. TMNT:SF won the NAVGTR award for Control Design, recognition that optimizing per input method, rather than compromising across all of them, was the right call.
The invisible work of cross-platform development is understanding what players on each platform consider standard and delivering it. If you don’t, they’ll assume you didn’t care about their platform.
Players judge quality not by absolute performance, but by whether you've met baseline expectations for their platform.
Production Truth #3: Platform Expertise Is Hard-Won Institutional Knowledge
Each platform holder runs a sophisticated ecosystem with its own submission structure, regional requirements, and certification logic. The complexity isn’t arbitrary. It reflects the scale of what these platforms manage globally. But first-time submissions on any platform come with a learning curve, and the studios that move fastest are the ones who’ve already paid that tuition.
Nintendo was our first console platform, and it set the tone for everything that followed. For a single update with DLC, you’re potentially managing:
- A main title page update, DLC store page, new trailer, bundle store pages, and patch build, all submitted separately, per region
- Regional release day requirements: Japan, Asia, and Korea release on Thursdays; everywhere else on Tuesdays
- Per-territory pricing setup and regional asset specifications
That’s potentially 25 submissions for a single update. We built a dedicated Nintendo submission runbook to manage it, a living document we update with every launch cycle. Complexity is manageable when you document it.
That discipline was tested at our Switch 2 launch. Two weeks before final submission, we discovered our digital build required its own separate PEGI certification, distinct from what we already held for the original Switch and our physical edition. It meant scrambling to create accounts, gather materials, and pay for rush processing. We got our approval three days before the deadline. The lesson: no matter how much institutional knowledge you’ve accumulated, new platforms will surface new requirements. The ability to adapt quickly is as important as the ability to plan ahead.
No matter how much institutional knowledge you've accumulated, new platforms will surface new requirements.
PlayStation taught us that the same feature can require entirely different workflows depending on how a player bought the game, and that game localization and storefront localization are separate workstreams that need to be planned independently. Two examples illustrate this:
- PS4-to-PS5 upgrades: We configured the upgrade path for our digital edition without issue. When our physical edition launched, players couldn’t access it. Physical editions use a separate upgrade product in Sony’s backend: same player-facing feature, entirely different approval workflow. It took nearly a month to resolve.
- Storefront languages: We localized TMNT:SF based on our target markets. PlayStation Store requires store text in languages determined by the regions you’re launching in, a different list entirely. We translated storefront materials into five additional languages to satisfy the requirement.
Understanding that PlayStation’s ecosystem treats these as distinct workstreams, regardless of how they appear to players, is now part of how we plan every launch on the platform.
The pattern across all of these: platform expertise accumulates. The first time through any of these processes is the hardest. The institutional knowledge we’ve built, documented in runbooks and carried by the team members who’ve been through each submission cycle, is part of what makes our cross-platform capability durable rather than one-time.
Cross-platform production at this scale is a discipline that has to be built, tested, and refined across every platform you ship on. The submission timelines, the player expectations, the platform-specific requirements: none of it is insurmountable, but none of it is obvious until you’ve been through it. The studios that do this well aren’t the ones with the biggest budgets. They’re the ones that treat each platform as a first-class commitment and build the institutional knowledge to back it up.
In a follow-up piece, I’ll cover what that discipline actually builds toward: the team, the infrastructure, and the capability that two years of cross-platform shipping made possible.
Craig Wells, Senior Director of Operations, Super Evil Megacorp