Production 101 - #15 Understanding Publishing Platforms
What producers need to know before their first cert submission
Game Production Alchemist › Production 101 › Game Publishing Platforms: What Producers Must Know
Every major platform has a certification framework, a submission portal, and a store CMS. The producer is usually the person navigating all three.
Sony’s TRC and Nintendo’s Lotcheck have specific timelines that will rearrange your launch window if you discover them too late.
IARC makes age rating compliance straightforward for digital releases. Physical ratings are a different, more expensive matter.
Platform documentation changes with each platform update. The producer’s job is knowing where to find the current spec, not memorising the last one.
The first time you submit a build to cert, the surprise is the realisation that almost everything you needed was public documentation the whole time. Every platform has a framework. Every framework has timelines. Every timeline has a way of colliding with your ship date if you discovered it too late. In smaller studios, the producer is typically the person who finds this out.
Why platform knowledge sits with the producer
In a large studio, platform relations is its own discipline. There are people whose entire job is managing the publisher relationship and navigating cert. In a smaller studio, the producer is that person. You’re the primary contact for the platform’s partner team, the one who manages the developer portal access, the one who reads the cert report and decides what the team needs to fix first.
Understanding the framework is the difference between a launch window you planned for and one you scrambled through.
This post covers the six platforms I’ve shipped on directly: iOS, Android, PlayStation, Xbox, Nintendo, and Steam. It doesn’t attempt a deep treatment of cert failure types, rejection reasons, or escalation paths. The goal is narrower: name the framework, explain the timeline, point to the portal. That’s enough to plan well.
What every platform has in common
Platform by platform, the differences are real, but the structure is the same. Every platform has a technical compliance framework, a submission process, a review timeline, a store or CMS where your product lives, and an age rating requirement.
Every producer shipping on a new platform for the first time should ask the same five questions. What is the certification framework called? How long does cert take? When does the store page need to be ready relative to launch? What age ratings are required for my target markets? Who is my primary contact in the platform’s partner team?
The answers vary. The questions don’t.
The platforms
PlayStation
Sony’s technical compliance framework is the TRC, the Technical Requirements Checklist. It covers DualSense features, trophy implementation, system integrations, error handling, and a range of other platform-specific requirements. The full TRC is available to authorised developers through the PlayStation Partners portal at partner.playstation.com, behind NDA.
One missed TRC can cost you weeks. Start validating against it during alpha. Not during submission.
After cert passes, Sony’s marketing and store team requires approximately four weeks to set up your store page from the assets you provide. That four-week window starts after cert passes, so treat the cert pass as the midpoint of your launch process. Factor those four weeks into your launch window from the beginning.
Xbox
Microsoft’s framework is the Xbox Requirements, abbreviated XRs. Cert typically takes four to seven business days. After cert, Microsoft’s Biz Ops team needs approximately two weeks to build out the store page from your submitted metadata, similar to the Sony store setup lag.
Microsoft offers an optional paid Certification service that provides early XR compliance feedback before formal submission. Worth considering if you’re uncertain about specific platform integrations. The developer portal is Xbox Partner Center at partner.microsoft.com/dashboard.
Nintendo
Nintendo calls their process Lotcheck. The name sometimes misleads producers who haven’t shipped on the platform before. Lotcheck checks platform compliance: Joy-Con behaviour, text handling, eShop integration, button art compliance, and rating compliance. Game bugs that fall outside those requirements are yours to find before submission. Expecting Lotcheck to catch them is a planning error.
Submit thirty days before your expected release date. Nintendo’s review timeline is longer than the console competition. The Nintendo Developer Portal at developer.nintendo.com holds the full guidelines once you’re authorised.
“Submit thirty days before your expected release date. Nintendo’s review timeline is longer than the console competition, and it will not flex to match your marketing window.”
iOS
Apple’s process is App Review. Ninety percent of reviews complete within 24 hours, but complex apps (those with in-app purchases, sensitive permissions, or account creation) can take three to seven days. Holiday periods extend timelines further.
Submitting Tuesday through Thursday during US business hours tends to produce faster turnaround than submissions near weekends or major holidays. This is anecdotal and not guaranteed, but it’s the pattern I’ve seen consistently across multiple submissions. The CMS is App Store Connect at appstoreconnect.apple.com.
Android / Google Play
Google Play Console at play.google.com/console is the submission and management interface. Google’s review process is generally faster than Apple’s. The Play Console also handles policy compliance, rating submissions via IARC, and staged rollout controls.
If you’re shipping simultaneously on iOS and Android, plan your submission windows so that iOS cert doesn’t create the bottleneck. Submit iOS first, or give yourself enough buffer that a slow App Review cycle doesn’t push the Android release date without reason.
Steam
Steam uses Steamworks for all developer and publishing functions. The partner portal is at partner.steamgames.com.
A few Steamworks-specific timelines that catch producers unprepared. New developers wait 30 days after paying the Steam Direct app fee (US$100 at time of writing) before they can publish. Your Coming Soon page needs to be live for at least 14 days before your release date. Store page review takes three to five business days. Build review takes one to five business days.
These timelines caught me off-guard on my first Steam release. The build review window felt obvious in hindsight, but the 14-day Coming Soon requirement and the 30-day new developer hold both required rescheduling. Factor all of them into your launch window, not just the build review.
Epic Games Store
The Epic Games Store serves a meaningful audience on PC. I haven’t shipped there directly, so this post doesn’t speak with authority on the cert framework or timelines. If you’re publishing on EGS, read the developer documentation directly rather than relying on secondhand accounts from developers on other storefronts.
Age ratings
Every major market has age rating requirements, and all the major platforms require valid ratings before approving your product for sale. You need them for every territory you’re selling into.
The International Age Rating Coalition, IARC, is the practical answer for digital games. It’s free and adopted by all the major digital storefronts: Xbox, Nintendo eShop, PlayStation Store, Google Play, and Steam. It works through a single questionnaire embedded in the storefront submission flow. That questionnaire generates ratings for multiple territories simultaneously: ESRB for North America, PEGI for Europe, USK for Germany, and others.
If you’re a digital-first studio, IARC is almost certainly your route. You go through the storefront submission flow and it’s already there.
“IARC is free, takes fifteen minutes, and handles multiple territory ratings from a single questionnaire. For digital releases, do it at the start of the submission process.”
Physical releases are a different matter. Traditional ESRB and PEGI certification for physical media is a paid process. PEGI certification for a physical release can run to several thousand euros, and the timeline is long. If you’re planning a physical SKU, factor both the cost and the submission lead time into your production budget and schedule from the start. Neither is trivial, and both are regularly underestimated by studios approaching their first physical release.
The physical rating cost surprises studios more than almost any other launch expense I’ve seen. It gets missed in early budgets because the team assumes digital ratings apply everywhere. Physical ratings require separate paid certification. Flag it early and put a number against it.
Store pages and CMS
Every platform has a content management interface where your store page lives: metadata, descriptions, screenshots, trailers, pricing, localisation. In smaller studios, the producer often owns this alongside cert submission.
App Store Connect’s review flow, the Xbox Partner Center store page builder, and Steamworks’ store page editor all have quirks that slow you down the first time you use them. Get into the interface before your launch window, not during it.
Cert passing and store going live are two separate events with their own timelines. The Sony four-week store setup and Nintendo’s thirty-day Lotcheck window are the two that most often catch producers out, because they sit on the far side of a cert pass that the team treated as the end of the line.
Building platform timelines into your schedule
Platform cert belongs in your milestone schedule as a fixed constraint with a buffer, anchored to your ship date and worked backward. Plan it at the start of production, with the same rigour as any other milestone.
For a simultaneous multi-platform launch: identify the longest cert window, which is usually Nintendo’s Lotcheck, set your first submission date from that, then verify the other platforms fit within the same window.
“The common planning error is setting a ship date, then calculating whether cert will fit. Set a cert date and let it drive the ship date.”
For each platform, you need three dates in your schedule. When the cert build needs to be ready. When store assets need to be submitted. When any platform-specific submissions (age ratings, store page review) need to happen. A platform cert calendar with those dates is a basic production artefact for any multi-platform release.
The producers who handle multi-platform launch well start the cert planning early, go back to the actual documentation each time, and treat the timelines as constraints rather than rough guides.
[INTERNAL LINK: Post #13 - How to Build a Milestone Schedule] [INTERNAL LINK: Post #14 - Scope Management and the Art of Cutting]
One more thing about documentation
Every platform updates its requirements periodically. The TRC changes. Lotcheck requirements change. App Review guidelines change. What was true on the last title may not be true on this one.
The producer’s job is knowing where to find the current spec and checking it at the start of each new project. Read the actual documentation. Memory from the last title drifts. Platforms update their requirements, and a requirement that passed on your last game may fail on this one. That check takes fifteen minutes at the start of a project and can save several weeks at the end of one.