3 ms·
The AppleWay (tm) has another problem: By displaying the last snapshot of the app as a splash screen, the Apple apps imply that you can immediately interact wi
by kbutler 16y ago
The AppleWay (tm) has another problem:
By displaying the last snapshot of the app as a splash screen, the Apple apps imply that you can immediately interact with the application - but you can't, because it's just a static image.
On slower hardware (e.g., the original iPhone/iPod Touch), this violation of user expectations can last for a measurable time - easily enough for the user to make multiple attempts to interact.
Touch...nothing happens. Touch...nothing happens.
A splash screen is better than a misleading "last view" snapshot.
Go with the night mode splash screen.
kb
- ugh 16y agoHe doesn’t and can’t use a last-view snapshot. He uses an empty UI with no content and no buttons, consequently it cannot be misleading. I would prefer that massively to a cheesy splash screen and a last-view snapshot, the only problem is that it doesn’t always fit.
- duopixel 16y agoThe 'last snapshot as a splash screen' actually traces back to Jeff Raskin's work on the Canon Cat. It counts on the user trying to remember where he left off while the program loads, so by the time you think "aha, I was gonna send an e-mail to Ron" the UI is responsive. It's a nice trick that saves you time in the end. Of course, if the app takes too long to launch the UI would seem unresponsive, which is why Apple chose to not make it available to third party developers.