- Zav
On May 15, 2012, at 01:35 PM, Jens Alfke <j...@mooseyard.com> wrote: On May 15, 2012, at 1:15 PM, Alex Zavatone wrote: Right after clicking on an app's icon, the splash screen/launch screen shows that the device has indeed paid attention to you and responded in the manner you expected, namely, the application has launched and is proceeding to load. I can not see how this is a bad idea. It’s psychological. Splash screens make the launch time *seem* slower. Ahhh, I disagree with this. If it stays up for a while, then there is a bigger problem. It is indeed psychological, and displaying something does tell the user that "yep, I, the device did respond to your action". I think it's worse to display a screen that looks like the first screen but one that they can't interact with. Now, if your app is going to take five or ten seconds to become responsive, then I’d agree you can’t just put up a picture of an empty UI — the user is going to notice that it’s not interactive and get really frustrated when her taps do nothing. But an app should not take that long to launch. My thoughts exactly. When I was at Apple the goal was always “one bounce” — on a cold launch the app’s Dock icon should bounce only once, and by that time the app should be ready to go. Tell that to the guys who make Safari. Even on last summer's MBP with 16 GB of RAM, I don't know many apps that take one bounce or less to launch - and I'm not talking about Photoshop. _______________________________________________ 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
