Dear list,

If an app uses iCloud to sync data between machines, should we provide the user 
a check-box to opt-out of iCloud syncing? Is there are recommended best 
practice here? What are others doing?

Reading the iCloud documentation I find this phrasing:

----
What user interface support is provided?

None. Your app is responsible for deciding what information (if any) to convey 
about iCloud support. In general, iCloud information should be conveyed 
seamlessly and involve minimal changes to your user interface.
----

This is from table 3-1 in the "iCloud Storage" section of the docs.

Should I interpret that as saying an app either supports iCloud, or doesn't. 
This should be seamless for the user, i.e., they should need (or be allowed to) 
switch iCloud on and off.

The reason I'm asking is that I can't see a good way to handle switching iCloud 
on/off and then handling the ensuing mess (missing transaction logs, conflicts, 
etc).

Anybody have any opinion on this? Somehow I'm loathed to force the user to sync 
over iCloud in my case (it's a shoebox core data app I'm talking about) because 
it seems a perfectly reasonable use-case to have different data sets on 
different machines. Equally well, some users may like to have their data sets 
synchronized with iCloud. So I'm confused as to how to proceed. With the old 
Sync Services, the activating/deactivating was a system level per-app switch 
for the user, and the system handled conflicts etc in a uniform way across all 
apps. Now we seem to be on our own.

Cheers,

Martin
_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to