3 ms·
Was it also not forbidden to have your app interpret code, which is the reason both for the still prevalent browser monoculture on iOS, originally (successfully
by llarsson 6y ago
Was it also not forbidden to have your app interpret code, which is the reason both for the still prevalent browser monoculture on iOS, originally (successfully) intended as a killer of Flash?
I suppose this is the same, in a way. They can't review what games will be played with a general-purpose game streaming app.
So this is to combat the "Flash" of today. Maybe?
(Not to mention that they can't get the 30% cut from every new game you happen to request via the app.)
- Macha 6y agoI believe you can still interpret code so long as all code that is interpreted is bundled in your app (so no pulling down code from your server at runtime). There was a C64 emulator way back that was allowed in with bundled legal homebrew, but it got pulled once it was discovered there was an "easter egg" to load arbitrary ROMs. A lot of the JS frameworks work this way, as well as Xamarin I think. If you want to A/B test, both versions need to present in your app and you can use a server side flag to switch between them, but you can't pull them dynamically, though some web view apps seem to get away with ignoring this.