How the programmes are structured
A platform holder does not sell you access to its hardware the way a retailer sells a console. It licenses it. Every studio that wants to ship on Nintendo Switch, PlayStation or Xbox must first be admitted to that holder's developer programme — a separate application, a separate agreement and a separate set of obligations for each platform. Nintendo's programme is NDP (Nintendo Developer Portal). Sony's is the PlayStation Partners programme. Microsoft runs ID@Xbox for independent developers and a separate managed programme for larger publishers. Three holders, three portals, three distinct sets of expectations.
The structural differences start at intake. Sony and Microsoft have for years offered self-publishing paths ↗ that allow an independent studio to apply without a publisher intermediary, provided it can demonstrate a viable project. Nintendo's programme has historically been more selective at the point of entry, though it has opened considerably since the Switch era: the hardware's commercial reach made a thin catalogue a strategic liability, so the gate lifted. Even so, admission to any of the three is not automatic. A studio demonstrates a real project, a real team and a legal entity; hobby applicants and holding companies without active development are typically turned away.
Once inside, the studio receives a development kit — the engineering hardware that exposes the platform's full capabilities, runs unsigned code and connects to the holder's proprietary toolchain. The development kit is not retail hardware with a switch flipped; it is a purpose-built unit, typically larger and with different thermal management, that gives the developer access to GPU and CPU counters, memory profilers and crash-logging infrastructure that the retail unit deliberately withholds. A kit is loaned, not sold, and its terms of use sit inside the programme agreement. The thermal budget the retail box operates under is the ceiling the dev kit maps, not the kit's own envelope.
Where the rules diverge
Each holder publishes a set of technical and content requirements that every submission must satisfy before it is approved to ship. Nintendo's requirements are called the Lotcheck guidelines; Sony's equivalent is the TRC — Technical Requirements Checklist; Microsoft uses the XR (Xbox Requirements) framework. The names differ. The underlying logic is identical: a documented checklist that a submission must clear before it reaches retail, because an unchecked release on a shared platform damages every other title on that platform. The holder is protecting the catalogue, not doing the studio a favour.
Where the programmes genuinely diverge is in what the requirements test for, how the test is run and how long it takes. Microsoft has historically run its certification process through an internal team with published turnaround windows. Sony runs its TRC compliance through platform-side certification engineers, and the process involves both automated passes and manual review; the timeline varies by submission complexity. Nintendo's Lotcheck process is known in practice for its rigour and its relative opacity — studios describe it as thorough, sometimes slow, and non-negotiable on its exact checklist items. A failure at Lotcheck returns a written report specifying the failing clause; it does not specify how to fix it.
The content rules also differ in ways that have historically mattered to certain genres. Nintendo's guidelines have been more restrictive on content ratings than Sony's, which track closely to regional ratings bodies — the ESRB ↗ in North America, PEGI in Europe — without imposing additional constraints above those bodies' own. A title that clears PEGI 18 does not automatically satisfy Nintendo's content requirements; there, the holder's own rules sit on top.
All three programmes impose obligations that persist after launch. A patch requires re-submission through the same gate. A title cannot be delisted unilaterally without going through the programme's removal process. The holder retains visibility over the product for its commercial life on that storefront, which is why the admission agreement is not a one-time transaction but an ongoing licence. The development kit goes back if the studio leaves the programme. The relationship is, and is meant to be, continuous.
