On May 15, 2012, at 3:10 PM, Conrad Shultz wrote: > If I were to model an app, and maybe Kyle can jump in here for obvious > reasons, I would pick OmniFocus. It sounds like it has similar broad > behaviors to what you're going for. When I open OmniFocus, here's the > sequence of events:
Yes, this is both what OmniFocus does and why it does it. But—importantly!—OmniFocus isn't special; it's following general best practice. Want to see other examples of this in action? Twitter, Mail, and Messages all do it. You might have to force-quit them to see the behavior in action, but they all start up with text-free screenshots as their Default.png, then quickly replace it with live UI, then populate that UI with whatever local content they can fetch quickly, then check for new content and update the content. You might consider disabling user interaction from the time your app starts loading to the time you've finished populating the UI with local data, in order to prevent the user from getting into a state that will just be disrupted when the local data has loaded. But you should _not_ load any significant amount data synchronously on the main thread, even if it's only local data. --Kyle Sluder _______________________________________________ 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
