It makes sense in a weird way, but it doesn’t feel right for a clock. You need to account for the case where it does take longer than it should to update, because sometimes it will for any number of really weird reasons. So you can’t just design for the best case scenario.
Now that you have a splash screen you need to ask yourself if it’s better to show the splash screen while doing the update, or to just let the app be unresponsive for the common case of a moment and then show the splash if it goes over that.
The answer is to show the splash in the common case too.
Now people are seeing a “weird screen” for a moment before they can process what they’re seeing. So you need to make the screen have a minimum display time to keep people from being confused.
It’s weird, but people can sometimes be more confused by thinking something happened too fast.
Good arguments for any given program, just hard to imagine they’re still valid for a clock. There’s no other example i can’t think of that a clock has noticeable startup delay or even update time. In the most charitable wording this is exceptional, a unique example amongst the broadest class of programs.
I now realize it’s probably not worth attempting to convince me to not be cynical, i’m having as much trouble as OP with this lol. Thanks for your thoughts though.
It makes sense in a weird way, but it doesn’t feel right for a clock. You need to account for the case where it does take longer than it should to update, because sometimes it will for any number of really weird reasons. So you can’t just design for the best case scenario.
Now that you have a splash screen you need to ask yourself if it’s better to show the splash screen while doing the update, or to just let the app be unresponsive for the common case of a moment and then show the splash if it goes over that.
The answer is to show the splash in the common case too.
Now people are seeing a “weird screen” for a moment before they can process what they’re seeing. So you need to make the screen have a minimum display time to keep people from being confused.
It’s weird, but people can sometimes be more confused by thinking something happened too fast.
Good arguments for any given program, just hard to imagine they’re still valid for a clock. There’s no other example i can’t think of that a clock has noticeable startup delay or even update time. In the most charitable wording this is exceptional, a unique example amongst the broadest class of programs.
I now realize it’s probably not worth attempting to convince me to not be cynical, i’m having as much trouble as OP with this lol. Thanks for your thoughts though.