The Switch is ARM and uses several components from FreeBSD and Android. It would not be surprising to learn that they have the ability to compile system components like Virtual Console for an ARM Linux with stubs for Switch-specific stuff.

The SNES Classic is also ARM, and has much less going on than the full Switch OS (Horizon). That could be the core of what they use for the museum displays, considering there’s an ARM version of Windows too.

Either way, devs gonna dev. If you can’t get feedback at your workstation and always have to deploy to your target platform to test anything, you’re gonna move too slow to catch and fix bugs or build flexible enough systems to prevent them.

So much of dev testing is about trade-offs between rapid iteration and thorough fidelity. You need access to both.

From my own experience, I’ve done stuff like:

• built mobile apps that can also be deployed as desktop apps or web apps for the sake of dev testing
• built testing tools for car systems that fake out sensor input
• built HTTP wrappers for cloud-deployed services to allow them to be run locally
• faked out camera feeds for AR apps

It can get janky, cuz not everything works the same way, but most of what you work on is not platform-specific anyway and a good architecture will minimize the portion of code that only works on the target platform.