In a recent development, Apple has blocked the release of UTM, a generic PC emulator for iOS devices, on the App Store. This move by Apple further clarifies its stance on mobile emulation and highlights the ongoing debate surrounding its boundaries.
The Emulation Evolving Landscape: Apple Rejects UTM PC Emulator for iOS
The decision comes after the US legalized emulation of older computer systems within the App Store framework. However, copyright concerns remain, as users should ideally possess the original game or program for legal emulation. Apple’s regulations employ the term “retro game console emulator,” which lacks clear definitions. Uncertainties arise regarding the age classification for “retro” and whether classic computer systems like the Commodore 64 qualify as “game consoles.”
Gizchina News of the week
Apple apparently differentiates between PCs and consoles. The company maintains that, despite the vast library of DOS and Windows games, PCs fundamentally differ from consoles. The UTM developer disagrees but has chosen not to contest the ruling due to performance limitations. Apple’s iOS platform restricts access to a critical feature known as the Just-In-Time (JIT) compiler. This absence significantly hinders emulation performance, potentially explaining Apple’s decision on UTM and foreshadowing the unlikely inclusion of emulators for newer consoles like the Nintendo GameCube or Wii.
For the App Store submission, the developer provided a special version, UTM SE, to address the performance concerns. This version would have explicitly informed users about the performance disparity compared to the original UTM, which remains available on the Mac App Store. Interestingly, the review process for UTM SE extended far beyond the usual timeframe, suggesting either a more complex review procedure or extended deliberation by Apple.
This episode sheds light on the evolving landscape of mobile emulation. Apple’s actions indicate a focus on retro console emulation, leaving the status of PC emulation ambiguous. The lack of a clear definition for “retro” and the exclusion of the JIT compiler on iOS further complicate matters. While the developer has conceded in this instance, the debate on mobile emulation boundaries is likely to continue.