拒绝应用程序：17.2：要求用户共享个人信息的应用程序 [英] Rejected App: 17.2: Apps that require users to share personal information

问题描述

前言：

我知道这个问题之前已在SO上提出过，但这些帖子已经过时了，我认为目前还不相关对Apple的决策。

拒绝原因：

17.2详细信息

我们注意到您的应用使用Facebook登录进行身份验证，但不包括该网站提供的基于帐户的功能，这在App Store上是不允许的。

后续步骤

请修改您的应用以包含该社交网络的基于帐户的功能或使用您自己的身份验证机制。

我的应用程序：

我的应用程序实现Facebook身份验证并获取用户的名字和仅限个人资料图片并由用户自行决定显示（当用户执行某项功能时）。

我向Apple说了两次，他们回答说这还不够。

他们一直在鹦鹉学舌，我需要添加Facebook的基于帐户的功能。我让他们详细说明，这些是我给出的例子：

在适用时实施朋友列表，社交图和游戏分数是合适的。 / p>

因此出现以下问题：

如果我的应用无法从中受益，该怎么办？上面的例子？

使用Facebook作为身份验证方法和获取基本数据有什么问题？

和踢球者 - 我可以实现哪些Facebook的基于帐户的功能的例子有资格获得使用Facebook身份验证的特权？

我确信我不会得到Apple的任何直接答案，所以我呼吁这里的专家希望能够启发我。

提前致谢。

解决方案

根据我对Apple Review Process的经验，最让他们困扰的是案例是：

• 如果您的应用强迫用户使用Facebook登录，并且不允许他/她以任何其他方式登录（或者根本不登录）。


• 如果您的应用没有基于帐户的功能，因为他们在拒绝详情中指明了这些功能（即使这些功能与Facebook没有特别关联。

您可以通过审核流程而不会损害应用的用户体验：

• 如果你不喜欢我们已经可以选择匿名使用该应用程序或使用电子邮件地址或任何其他非Facebook身份验证方式登录，您一定要添加一个。这不仅可以增加您的应用获得Apple批准的机会，还可以为您的用户提供尝试应用的方式，而无需向您提供他们的Facebook信息。许多用户在使用他们宝贵的Facebook帐户登录之前需要在应用程序中获得信任，因此这实际上可以帮助您登机，并且强烈建议。


• 添加一些帐户特定功能到你的应用程序。它不一定是Facebook特定的数据。它可以说服审核小组你不仅仅是在收集有关用户的数据，还可以为他们提供某些好处，因为他们已经登录。例如，这可以是与游戏相关的功能，例如Apple建议：分数，排行榜，朋友列表，邀请，奖励，聊天等。它也可以是非游戏相关的。例如：内容管理（允许用户根据他/她的帐户保存数据并在以后访问，喜欢应用程序中的某些元素，在一个地方保存应用程序相关内容，在Facebook上共享内容等。


• 您可以做的最好的事情（如果它适用于您的应用）只是为您的应用中的用户找到了一些意义。这将为用户必须登录带来意义。如果您有这样的，即使它不一定与Facebook有关，你也应该好好去。

这个例子对两者都有好处。审核团队和你的应用程序传播病毒的机会，相对廉价实施，将添加邀请朋友使用该应用程序的能力。这将证明登录Facebook并为您的用户提供额外的价值是合理的。但是，我强烈建议不要强迫用户登录，除非绝对必要。让他/她了解你的应用，学会喜欢它然后，当他/她信任你并愿意提交，然后你给他们登录的选项。如果它来自他们而不是因为他们必须这样做，那么您的用户在登录应用程序时感觉良好和安全的可能性要高得多。

我希望这样帮助，甚至一点点。祝你好运！

Preface:

I know this issue has been raised here before on SO, but those posts are old and I believe not currently relevant to Apple's decision making.

Rejection reason:

17.2 Details

We noticed that your app uses Facebook login for authentication purposes but does not include account-based features offered by that site, which is not allowed on the App Store.

Next Steps

Please modify your app to include account-based features of that social network or use your own authentication mechanism.

My App:

My App implements Facebook authentication and grabs the user's first name and profile picture only and displays them at the user's discretion (when the user performs a certain function).

I stated this to Apple twice and they replied that this was not enough.

They kept parroting that I needed to add "account-based features" of Facebook. I asked them to elaborate and these were the examples I was given:

"It would be appropriate to implement friends lists, social graphs, and game scores when applicable. "

So these questions arise:

What if my app doesn't benefit from the above examples?

What's wrong with using Facebook as an authentication method and for grabbing basic data?

And the kicker - what are more examples of "account-based features" of Facebook that I could implement that would qualify for the privilege to use Facebook authentication?

I'm sure I won't get any straight answers from Apple, so I am appealing to the experts here to hopefully enlighten me.

Thanks in advance.

解决方案

Based on my experience with the Apple Review Process, what bothers them most in this case is:

• If your app "forces" the user to login with Facebook and doesn't allow him/her to login any other way (or not login at all).
• If your app has no "account-based features" as they indicate in their rejection details (even if these features are not specifically related to Facebook.

Things you can do to pass the review process without damaging your app's user experience:

• If you don't already have an option to use the app annonymously or login with an email address or any other non-Facebook method of authentication, you should definitely add one. Not only will that increase your app's chances of being approved by Apple, it will also provide your users a way to try your app without providing you with their Facebook information. A lot of users need to gain trust in an app before logging in with their precious Facebook account, so this can actually help your on boarding process and is highly recommended.
• Add some account specific features to your app. It doesn't necessarily have to be Facebook specific data. It can be anything that will convince the review team that you're not just collecting data about your users, you are also providing them with some sort of benefit because they logged in. Examples for this can be game related features, like Apple suggested: score count, leader boards, friends list, invitations, rewards, chats, etc. It can also be non gaming related. Things like: content management (allowing the user to save data based on his/her account and accessing it later, "liking" certain elements in the app, saving app related content in one place, sharing content on Facebook, etc.
• The best thing you can do (if it works for your app) is just find some significance to a "user" in your app. Something that will give meaning to the user's having to login. If you have that, even if it's not necessarily Facebook related, you should be good to go.

An example that can be good for both the review team and your app's chances of going viral, which is relatively "cheap" to implement, would be to add the ability to invite friends to use the app. This would justify logging in with Facebook and give your users an extra value. However, I would highly recommend not forcing the user to login unless it's absolutely necessary. Let him/her learn about your app, learn to love it and then, when he/she trusts you and is willing to "commit", then you give them the option to login. When it comes from them and not because they had to, the chances of your user feeling good and safe about logging in to your app, is significantly higher.

I hope this helps, even a little. Good Luck!

这篇关于拒绝应用程序：17.2：要求用户共享个人信息的应用程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！