Apple App Store: Difference between revisions

Line 109:

==JIT==

~~Safari is allowed to~~ [[wikipedia:Just-in-time compilation|~~just~~-in-~~time]] compile~~ code ~~worldwide. The super short version~~ of ~~what that means: it can run JavaScript~~ code ~~''really fast''~~. ~~All browsers~~, and ~~other runtimes~~ like ~~Microsoft .NET~~, ~~Java~~, Lua ~~use this~~. ~~Ok, fine, it's the system web browser, it's very carefully written to be secure, and it's important to the platform to be doing well in performance benchmarks and all that~~.

[[wikipedia:Just-in-time compilation|JIT]], which stands for Just-In-Time, is a method of compilation where code, instead of being compiled before being distributed (like an EXE), gets compiled into machine code in real time before being executed. This method of compilation allows for much faster loading times (when talking about websites), faster emulation (when emulating a different architecture) and faster program execution (when executing a program written in an interpreted language like JavaScript, Python, Lua...)

Apple's [https://apps.apple.com/app/swift-playgrounds/id908519492 Playgrounds] app on iPad is also allowed to JIT. It bundles Apple's [[wikipedia:Swift (programming language)|Swift]] compiler, and shares backend code with the version of Playgrounds found in [[wikipedia:Xcode|Xcode]].

Safari is allowed to use the JIT compiler to compile code from any site, and Apple's [https://apps.apple.com/app/swift-playgrounds/id908519492 Playgrounds] app on iPad is also allowed to use JIT. Playgrounds bundles Apple's [[wikipedia:Swift (programming language)|Swift]] compiler, and shares backend code with the version of Playgrounds found in [[wikipedia:Xcode|Xcode]].

Competing apps like Pythonista (a Python IDE), emulators like Delta and UTM, and terminal environments like iSH, are not allowed to JIT~~. As such~~, ~~they need~~ to ~~rely on inferior~~ performance~~, potentially from an entirely separate implementation of their compiler/interpreter that may be less proven, because the JIT-less implementation doesn't need to exist on any other platform~~.

Competing apps like Pythonista (a Python IDE), emulators like Delta and UTM, and terminal environments like iSH, are not allowed to use JIT, instead having to interpret code, which comes with serious performance degradation and is more computationally expensive.

~~Likely the most clear~~ example is UTM SE. UTM is a port of ~~the~~ [[wikipedia:QEMU|QEMU]] ~~emulator to~~ iOS, allowing ~~you~~ to run ~~desktop~~ OSes ~~(Linux, Windows 98, XP, classic Mac OS, etc)~~. iPhone hardware ~~is very~~ capable ~~these days and it runs impressively well~~, '~~'if'' you use a hack to enable~~ JIT ~~(which Apple has now patched). "SE" stands for "slow edition" - yes, really. If you compare~~ the ~~true version of~~ UTM to ~~the App Store~~ UTM SE ~~app, you~~ '~~'will'' feel the loss in performance. It's impressive UTM even got to be on the App Store at all~~, ~~and the DMA~~ is ~~to thank~~ for it. ~~But~~ Apple ~~is still holding~~ the ~~line on allowing~~ JIT to apps that ~~require~~ that ~~performance~~.

An example of apps being heavily affected by this restriction is UTM SE. UTM is a port of [[wikipedia:QEMU|QEMU]] for iOS, iPadOS and MacOS, allowing users to create [[wikipedia:Virtual_machine|VMs]] that can run various OSes. The iPhone's hardware capable enough to emulate various OSes at full speed, but due to Apple's JIT limitation the team behind UTM had to create UTM SE (slow edition) that doesn't require JIT, but is nowhere near as fast as UTM with JIT. While methods that enable JIT for apps other than Safari and Playgrounds exist (some currently working on iOS 18.5), Apple does not allow the use of JIT in notarized apps, meaning that programs that support JIT will have to be sideloaded, which comes with its own set of restrictions.

~~While UTM SE releasing at all might seem like a pathway~~ to ~~getting Firefox~~ and ~~Chrome "slow editions" on the App Store, browser~~ engines other than the built-in Apple WebKit/JavaScriptCore are still outlawed.<ref>{{Cite web |title=App Review Guidelines |url=https://developer.apple.com/app-store/review/guidelines/#2.5.6 |url-status=live |access-date=16 Mar 2025 |website=[[Apple Developer]]}}</ref> In the EU, ~~Apple has blessed web browser JavaScript engines~~ with the option to use JIT. The ~~app must~~ be approved for an entitlement, and then must work within APIs provided by Apple for it. As of January 2025, no browsers have been released ~~using this. We were all anticipating proper competition around web browsers on iOS~~, ~~but almost a year later~~, ~~we have nothing~~.<ref>{{Cite web |title=Mozilla says Apple’s new browser rules are ‘as painful as possible’ for Firefox |url=https://www.theverge.com/2024/1/26/24052067/mozilla-apple-ios-browser-rules-firefox |url-status=live |access-date=16 Mar 2025 |website=[[The Verge]]}}</ref>

In the EU, Apple gave web browsers permission to use rendering and JavaScript engines other than the built-in with Apple WebKit/JavaScriptCore, with the option for JS engines to use JIT. The browser still has to be approved for an entitlement, and then must work within APIs provided by Apple for it. But, as of January 2025, no browsers that use different engines than the built-in ones have been released, mainly due to arbitrarily imposed restrictions, meant to discourage the usage of third-party engines.<ref>{{Cite web |title=Mozilla says Apple’s new browser rules are ‘as painful as possible’ for Firefox |url=https://www.theverge.com/2024/1/26/24052067/mozilla-apple-ios-browser-rules-firefox |url-status=live |access-date=16 Mar 2025 |website=[[The Verge]]}}</ref>

However, Apple still does not allow different engines outside of the EU, with or without JIT support.<ref>{{Cite web |title=App Review Guidelines |url=https://developer.apple.com/app-store/review/guidelines/#2.5.6 |url-status=live |access-date=16 Mar 2025 |website=[[Apple Developer]]}}</ref>

==Sandbox==

@@ Line 109: / Line 109: @@
 ==JIT==
-Safari is allowed to [[wikipedia:Just-in-time compilation|just-in-time]] compile code worldwide. The super short version of what that means: it can run JavaScript code ''really fast''. All browsers, and other runtimes like Microsoft .NET, Java, Lua use this. Ok, fine, it's the system web browser, it's very carefully written to be secure, and it's important to the platform to be doing well in performance benchmarks and all that.
+[[wikipedia:Just-in-time compilation|JIT]], which stands for Just-In-Time, is a method of compilation where code, instead of being compiled before being distributed (like an EXE), gets compiled into machine code in real time before being executed. This method of compilation allows for much faster loading times (when talking about websites), faster emulation (when emulating a different architecture) and faster program execution (when executing a program written in an interpreted language like JavaScript, Python, Lua...)
-Apple's [https://apps.apple.com/app/swift-playgrounds/id908519492 Playgrounds] app on iPad is also allowed to JIT. It bundles Apple's [[wikipedia:Swift (programming language)|Swift]] compiler, and shares backend code with the version of Playgrounds found in [[wikipedia:Xcode|Xcode]].
+Safari is allowed to use the JIT compiler to compile code from any site, and Apple's [https://apps.apple.com/app/swift-playgrounds/id908519492 Playgrounds] app on iPad is also allowed to use JIT. Playgrounds bundles Apple's [[wikipedia:Swift (programming language)|Swift]] compiler, and shares backend code with the version of Playgrounds found in [[wikipedia:Xcode|Xcode]].
-Competing apps like Pythonista (a Python IDE), emulators like Delta and UTM, and terminal environments like iSH, are not allowed to JIT. As such, they need to rely on inferior performance, potentially from an entirely separate implementation of their compiler/interpreter that may be less proven, because the JIT-less implementation doesn't need to exist on any other platform.
+Competing apps like Pythonista (a Python IDE), emulators like Delta and UTM, and terminal environments like iSH, are not allowed to use JIT, instead having to interpret code, which comes with serious performance degradation and is more computationally expensive.
-Likely the most clear example is UTM SE. UTM is a port of the [[wikipedia:QEMU|QEMU]] emulator to iOS, allowing you to run desktop OSes (Linux, Windows 98, XP, classic Mac OS, etc). iPhone hardware is very capable these days and it runs impressively well, ''if'' you use a hack to enable JIT (which Apple has now patched). "SE" stands for "slow edition" - yes, really. If you compare the true version of UTM to the App Store UTM SE app, you ''will'' feel the loss in performance. It's impressive UTM even got to be on the App Store at all, and the DMA is to thank for it. But Apple is still holding the line on allowing JIT to apps that require that performance.
+An example of apps being heavily affected by this restriction is UTM SE. UTM is a port of [[wikipedia:QEMU|QEMU]] for iOS, iPadOS and MacOS, allowing users to create [[wikipedia:Virtual_machine|VMs]] that can run various OSes. The iPhone's hardware capable enough to emulate various OSes at full speed, but due to Apple's JIT limitation the team behind UTM had to create UTM SE (slow edition) that doesn't require JIT, but is nowhere near as fast as UTM with JIT. While methods that enable JIT for apps other than Safari and Playgrounds exist (some currently working on iOS 18.5), Apple does not allow the use of JIT in notarized apps, meaning that programs that support JIT will have to be sideloaded, which comes with its own set of restrictions.
-While UTM SE releasing at all might seem like a pathway to getting Firefox and Chrome "slow editions" on the App Store, browser engines other than the built-in Apple WebKit/JavaScriptCore are still outlawed.<ref>{{Cite web |title=App Review Guidelines |url=https://developer.apple.com/app-store/review/guidelines/#2.5.6 |url-status=live |access-date=16 Mar 2025 |website=[[Apple Developer]]}}</ref> In the EU, Apple has blessed web browser JavaScript engines with the option to use JIT. The app must be approved for an entitlement, and then must work within APIs provided by Apple for it. As of January 2025, no browsers have been released using this. We were all anticipating proper competition around web browsers on iOS, but almost a year later, we have nothing.<ref>{{Cite web |title=Mozilla says Apple’s new browser rules are ‘as painful as possible’ for Firefox |url=https://www.theverge.com/2024/1/26/24052067/mozilla-apple-ios-browser-rules-firefox |url-status=live |access-date=16 Mar 2025 |website=[[The Verge]]}}</ref>
+In the EU, Apple gave web browsers permission to use rendering and JavaScript engines other than the built-in with Apple WebKit/JavaScriptCore, with the option for JS engines to use JIT. The browser still has to be approved for an entitlement, and then must work within APIs provided by Apple for it. But, as of January 2025, no browsers that use different engines than the built-in ones have been released, mainly due to arbitrarily imposed restrictions, meant to discourage the usage of third-party engines.<ref>{{Cite web |title=Mozilla says Apple’s new browser rules are ‘as painful as possible’ for Firefox |url=https://www.theverge.com/2024/1/26/24052067/mozilla-apple-ios-browser-rules-firefox |url-status=live |access-date=16 Mar 2025 |website=[[The Verge]]}}</ref>
+However, Apple still does not allow different engines outside of the EU, with or without JIT support.<ref>{{Cite web |title=App Review Guidelines |url=https://developer.apple.com/app-store/review/guidelines/#2.5.6 |url-status=live |access-date=16 Mar 2025 |website=[[Apple Developer]]}}</ref>
 ==Sandbox==