Apple revamps app store guidelines, sets new rules for remote mirroring apps like steam link – mac rumors database collation

There are several tweaks that have been made to the App Store Guidelines, and one notable change appears to have been introduced specifically because of the Steam Link debacle that saw Apple approve and then renege on the Steam Link app for iOS.

A new guideline, 4.2.7, says that all Remote Application Mirroring apps, such as Steam Link, must comply with a specific set of rules. Such apps are not allowed to offer a user interface that resembles an App Store view or a store-like interface, nor can they include the ability to purchase software not already owned by the user. Apple is allowing transactions to be made by remote mirroring apps, as long as purchases are made on the host device rather than the iOS device. The UI appearing on the client does not resemble an iOS or App Store view, does not provide a store-like interface, or include the ability to browse, select, or purchase software not already owned or licensed by the user.

For the sake of clarity, transactions taking place within mirrored software do not need to use in-app purchase, provided the transactions are processed on the host device.With the clarification of Apple’s stance on games streamed from a PC or Mac, the Steam Link app may be able to launch on iOS devices after all. Valve has not yet commented on the policy changes, and it’s not clear what Valve will need to tweak to comply with the new rules.

There are multiple other changes to the App Store Guidelines. A modified 3.1.1 rule, for example, says that non-subscription apps may offer a free time-based trial period using a free in-app purchase option that temporarily unlocks app functionality. This will allow all apps in the App Store to offer free trials, rather than just subscription apps.

Apps that offer auto-renewing subscriptions, meanwhile, are prohibited from attempting to trick users into purchasing a subscription under false pretenses or engaging in bait-and-switch practices. Such apps will be removed from the App Store.

A new rule, 2.3.12, states that all apps are required to "clearly describe" new features and product changes in their "What’s New" text. Apps can continue to use generic descriptions for bug fixes, security updates, and performance improvements, but anything more significant must be listed in the notes.

Apps are also now required to obtain explicit user consent and provide a clear visual indication when recording or making a record of user activity, and there’s a new rule that says apps can use Unicode characters that render as Apple emojis within apps and app metadata, a change from earlier this year when some apps were rejected for using emojis in their App Store descriptions. Emojis can’t be embedded directly into an app binary, however.

Am I being thick, or does this not increase clarity at all? The first half seems to say no store (in the UI appearing on the client, which is where it appears when it’s mirrored), then second half seems to say it’s OK if it’s processed on the host. We’re talking about a mirrored UI, meaning it’s processed on the host but displayed on the client. So is it OK or isn’t it?

My interpretation is that the first sentence pertains to the client/iOS app itself, while the second sentence pertains only to the host machine. By "UI appearing on the client", I think that means that the iOS app itself cannot have a way to directly purchase or select already-purchased software. So an iOS app can’t load a table of Steam games for instance. This would exclude using both iOS’s native table and web views for displaying Steam games as both UI elements are generated on the client side. From the second sentence, I think that this means you can access a Steam game if the Steam app itself or a browser are what’s being mirrored as that UI is generated on the host side. Yes, perhaps technically this is "UI appearing on the client", but it’s not UI generated by the client–from the client’s perspective, it’s just content being mirrored.