![]() ![]() While CloudKit is more transactional and under your explicit control, CloudKit operations are designed to ensure data committed arrives in iCloud storage even if the app is exited or the user signs out.Ĭheck out the iCloud Design Guide for which storage API is best for your app.Jamf Setup and Jamf Reset with Single Login Enhances iPhone and iPad Shared Device Management for Frontline Workers Implementing support for iCloud Documents and Key-Value Storage APIs means your user content will be in-sync without having to explicitly manage that synchronization process. Storing credentials and other lightweight information in Keychain via Keychain Services API ensures they will be secure and available wherever the user signs in.įor more information on Keychain implementation, check out the Keychain Services Programming Guide. Keychain on Shared iPad provides automatic synchronization across devices using the same Apple ID. ![]() Apps using NSURLSession with the appropriate background configuration to push user-specific settings or data will be assured that their uploads will continue after the user has switched apps and more importantly after the current user has signed out on a Shared iPad.įor more information on NSURLSession, watch the WWDC video Networking with NSURLSession and review NSURLSession Class Reference. Doing so indicates that your app supports having its local data purged when the user logs out. Indicate support for Shared iPad by setting the NSSupportsPurgeableLocalStorage key to “yes” in your project’s ist. Indicate purgeable local storage support in your project PList. These APIs provide support to continue the network operation without blocking the transition between users. Limit the amount of work you do in background task assertions to the minimum needed to ensure data consistency and synchronization - generally calls to NSURLSession or iCloud APIs to upload the user’s data. Limit background task assertion requirements. If your app determines the need for a first launch experience based on a flag currently stored in the local file system or NSUserDefaults, you should move these per user flags to NSUbiquitousKeyValueStore and check there before presenting your first launch experience.įor more information on the NSUbiquitousKeyValueStore, check out the NSUbiquitousKeyValueStore Class Reference and PrefsInCloud sample project. Store first launch or progress flags in the cloud. Be sure to synchronize during applicationWillResignActive at the minimum, but keep in mind that waiting too long or holding an overly large batch for synchronization will provide an inferior user experience and may lead to data loss in rare cases. Sync user entered or created data as you get it. Rather than bringing back all known user content you may need in the app, consider only pulling what’s required in the current context. Since all data associated with a given app may not be required at any given time, develop a download strategy that ensures you only download what’s needed when it’s needed or just before. Send data to your own backend using NSURLSession, or use iCloud, NSUbiquitousKeyValueStore and store credentials in Keychain.įetch remote data on demand. Shared iPad requires a cloud-based synchronization model for any data required to persist between uses of the app. This will show customers using Apple School Manager that your app works well with Shared iPad. Doing so indicates that your app supports having its local data purged when the user signs out. Once you’ve implemented the Data Management and Sync best practices, you’ll want to indicate your support for Shared iPad by setting the NSSupportsPurgeableLocalStorage key to “yes” in your project’s ist. Supporting purgeable local storage means that you either have no persistent content of consequence (for example, a calculator app), or your app ensures that any content that requires persistence is stored in the cloud. This case also covers the unlikely event that Shared iPad has to purge the data for a given user or app. If your app picks up where you left off, your app supports Shared iPad. Sign in to a second iPad using the same Apple ID.Sign out of your Apple ID on this iPad.Interact as a user by creating, changing, or adding content.Run your app on an iPad that’s signed into your Apple ID.If your app is cloud-based or doesn’t store data locally, your app may already support Shared iPad.* You can test if your app works well with Shared iPad by doing the following with two single-user iPad devices signed in with the same Apple ID: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |