"IOS Human Interface Guidelines"--accessing User Data

Accessing user Data

Location services allow apps to determine the approximate location of people, the direction in which their devices are pointing, and the direction they move. Other system services-such as contacts, calendars, reminders, and albums-also allow the app to access the data that the user stores.

Even when people love apps that know a lot about the convenience of their information, they also want to be able to choose the privacy that protects their data. For example, people like to be able to automatically mark their physical location or find nearby friends, but they also want to disable these features when they choose not to share their location with others. (View location and Maps Programming Guide to learn more about how to get your app to target content.) ）

The following guidelines can help you get user data in a way that users feel comfortable with.

Make sure users understand why they are being asked to share their private data. If people do not see a clear need for data, they will naturally be suspicious of asking for their personal information. To avoid making users uncomfortable, make sure to display a warning box only when they try to use a feature that clearly needs to know their information. For example, people can use maps when the service is closed, but they will see a warning box when they use the feature to find and track their current location.

if it's not obvious, describe why your app needs information. you can provide the text displayed in the warning box, placed on the system provided such as "' app name ' want to use your contacts" or for location notifications, "Allow ' app name ' to use your location when you use the app?" "Under the heading. You will want this text to be clear and polite, so that people will understand why you are asking to connect their information and not feel pressured.

The text of your reason should be:

• Does not include the name of your app. The system-provided warning header already contains your app name.

• Clearly describe why your app needs this data. If appropriate, you can also explain the way your app does not apply the data.

• Use user-centric terminology and localization.

• As short as possible, but still easy to understand. Try not to exceed one sentence as much as possible.

• Use sentence style capitalization. (sentence style capital refers to the first letter is uppercase, the other letters are lowercase, unless it is a proper noun and a proprietary adjective.) ）

Request data permission only when your app is launched without user data being unable to perform major functions. If it's obvious that your app's main function depends on knowing people's personal data, they won't be bothered.
Do not program trigger warning boxes before the user chooses the attributes that require the data. This way, you can avoid asking users to wonder why your app wants their private data when they do something they don't need. (Note that checking the user's location service preference does not leave the warning box.) ）
for location data, check location service preferences to avoid triggering warning boxes unnecessarily. You can use the core location programming interface to get this setting (see Core location Framework reference learn how). With this knowledge, you can trigger a warning box whenever possible when you request location information, or you may not have a warning box at all.

This article is translated from the official Apple development document to view the integration set: Https://github.com/Cloudox/iOS-Human-Interface-Guidelines All rights reserved: Http://blog.csdn.net/cloudox_

"IOS Human Interface Guidelines"--accessing User Data