Guideline 2.3.1 - Performance (open link in safari)

Hi,

My game has been rejected based on the following:

We discovered that your app contains hidden features. Specifically, this app contains functionality to load a webview of external content within the app. It would be appropriate to ‘bake-in’ content of these web pages into the submitted binary or remove them from the app’s functionality before resubmitting for review.

I do have a attribution screen that i credit people who have helped me with the game and link (opens externally in Safari) to their Instagram/SoundCloud/behance/email accounts.

Is this not allowed?

Answered by Claude31 in 710816022

Is this not allowed?

That's apparently what the reviewer thinks.

  • in 2.3.1

How do you present the link to users ? Is it clear what the links connects to ? Visibly, that was not clear for the reviewer until he/she fired the link. That's probably part of the problem.

There are several other requirements on links in Appstore :

  • 1.3 Kids Category: The Kids Category is a great way for people to easily find apps that are designed for children. If you want to participate in the Kids Category, you should focus on creating a great experience specifically for younger users. These apps must not include links out of the app, 

  • 3.1.3(a) “Reader” Apps: Apps may allow a user to access previously purchased content or content subscriptions (specifically: magazines, newspapers, books, audio, music, and video). Reader apps may offer account creation for free tiers, and account management functionality for existing customers. Reader app developers may apply for the External Link Account Entitlement to provide an informational link in their app to a web site the developer owns or maintains responsibility for in order to create or manage an account. Learn more about the External Link Account Entitlement.

Are this web pages dynamic or not ?

My advice would be:

  • as require, bake-in the pages
  • add a "know more button" to connect to the web pages if they are dynamic. If not, no need. Make it very clear and explicit for user.
  • Explain very clearly to reviewer in comments what are those web pages.
Accepted Answer

Is this not allowed?

That's apparently what the reviewer thinks.

  • in 2.3.1

How do you present the link to users ? Is it clear what the links connects to ? Visibly, that was not clear for the reviewer until he/she fired the link. That's probably part of the problem.

There are several other requirements on links in Appstore :

  • 1.3 Kids Category: The Kids Category is a great way for people to easily find apps that are designed for children. If you want to participate in the Kids Category, you should focus on creating a great experience specifically for younger users. These apps must not include links out of the app, 

  • 3.1.3(a) “Reader” Apps: Apps may allow a user to access previously purchased content or content subscriptions (specifically: magazines, newspapers, books, audio, music, and video). Reader apps may offer account creation for free tiers, and account management functionality for existing customers. Reader app developers may apply for the External Link Account Entitlement to provide an informational link in their app to a web site the developer owns or maintains responsibility for in order to create or manage an account. Learn more about the External Link Account Entitlement.

Are this web pages dynamic or not ?

My advice would be:

  • as require, bake-in the pages
  • add a "know more button" to connect to the web pages if they are dynamic. If not, no need. Make it very clear and explicit for user.
  • Explain very clearly to reviewer in comments what are those web pages.

Hi Claude31,

Thanks for taking the time to answer.

How do you present the link to users?

Is it clear what the links connects to? Visibly, that was not clear for the reviewer until he/she fired the link. I guess this is a definite possibility

Are this web pages dynamic or not? They are profile pages - so dynamic

So from what I'm understanding - my buttons are not showing their intention clearly.

Either I rework the UI (your "know more" button) and still possibly be rejected or I forgo opening up a webpage and just show the contributors username meaning the actual user would have to manually search on the particular social media platform (not very convenient).

I will implement the "know more" option as it provides a better user experience (IMO) and I should be able to resubmit if that is rejected again.

Guideline 2.3.1 - Performance (open link in safari)
 
 
Q