The Elusive Switch 2 Dev Kits: A Developer's Dilemma

The Switch 2 has burst onto the scene with remarkable speed, with Circana's latest data revealing a 75% lead over the original Switch's sales at the same point in its lifespan. This success is not limited to the US, as estimates from other markets also indicate a global phenomenon. The pent-up demand for a Switch successor, combined with Nintendo's impressive inventory and supply chain management, has resulted in a runaway hit. If the company can maintain its supply chain and keep shelves stocked throughout the winter, it will likely achieve the strongest opening year of any console in history. However, this success may be rubbing salt in the wound for developers who have not yet received a Switch 2 dev kit. Although hard numbers are difficult to come by, industry chatter surrounding Switch 2 has centered on the numerous studios, including those with notable releases, still awaiting development hardware. Most developers are tight-lipped about their experiences with Nintendo, which is notoriously sensitive about its behind-the-scenes business being reported in the press. Nevertheless, it is noteworthy that many people are willing to privately express their frustrations to journalists about the lack of access to dev kits, as reported by Digital Foundry and others. It is possible that a large shipment of dev kits is on the way, and the issue will be resolved in a few weeks. However, this seems unlikely, especially given that some studios are being advised to focus on Switch 1 development and rely on backwards compatibility to reach Switch 2 players. Conspiracy theories have emerged regarding the dev kit shortage, with some speculating that it is an attempt to control access to the hardware and protect it from potential hackers. However, this explanation does not hold up in practical terms, as it is largely a reflection of consumers' ongoing focus on Nintendo's efforts to crack down on unauthorized system use. A more plausible explanation is that Nintendo is attempting to exert quality control over early third-party Switch titles by prioritizing dev kit access for teams that have passed an internal vetting process. However, this criteria seems unusual, as some small studios with limited track records have received dev kits, while more established teams have been left out. Alternatively, Nintendo may be trying to control the transition between Switch and Switch 2, ensuring that the early success of Switch 2 does not result in a drought of third-party software for the original Switch, which still has a large active user base. Given that it is possible to develop Switch titles that benefit from Switch 2's higher specs, it is credible that the company would want to encourage developers to pursue this path, especially since Switch sales remained strong until the launch of its successor. The issue is that all these explanations rely on the assumption that there is a strategy in place, which may not be the case. It is equally likely that Nintendo is simply falling back into old habits. Historically, supporting third-party developers, particularly smaller and independent studios, has not been Nintendo's strong suit. Looking back at the launch of previous Nintendo systems, complaints from developers are eerily similar to those being heard today. Unlike Sony and Microsoft, which built their console businesses around encouraging and supporting third-party developers before developing their own strong studio line-ups, Nintendo has primarily focused on developing first-party software for its own platforms. Third-party releases have been secondary, with support for smaller partners being a low priority in the early stages of console lifespans. This has often resulted in limited access to development hardware, with some developers complaining of weak support even for those with dev kits. While Nintendo's perspective may make sense commercially, it offers little comfort to studios that cannot start working on Switch 2 titles despite the console's millions of sales. The commercial prospects for releasing on Switch 2 make it difficult for developers to ignore, but the path to market seems frustrating and uneven for many studios. The silver lining is that on previous Nintendo platforms, these issues have largely been resolved over time, with access to dev kits becoming more plentiful and less haphazard as the months pass. Although this is little comfort to studios with games well-suited to Switch 2, which are currently waiting for the necessary hardware to start development in earnest. Nintendo will always march to its own beat. We can only hope that the coming months will see the company's handling of third-party developers improve.