Comment: shortsighted rant (Score 1) 461
There aren't many apps that instantly show up on your phone/tablet (unless they were already running in the background).
I even hate it when an application DOESN'T have a splashscreen (like firefox or IE), I have to wait and guess if something is happening before the actual application is shown.. A good application that has any loading needed should show a splash/loadingscreen, so a user knows something is happening, best is also to actually have a progressbar/object, or a line which flashes a lot of texts with what it's loading. It might slow the real loading for a bit maybe, but not the perception to the user, as he/she see's something is happening.. The lack of a loadingscreen (and therefore a long waiting time between the actual double click and seeing the first screen) is a big indication of lack of userinteraction knowledge.. ofcourse the best thing would be not having a loadingtime at all, but since you are targeting a large crowd, you have to keep in mind that there are people with slow devices/computer and people with superduperhyperfast devices/computers, you'll keep them both happy, as the slow one actually sees something happening, and the fast ones don't notice it, as it's gone before they blinked their eyes.. so the first line of code in an application that has something to load, is showing the splashscreen, and then go ahead with loading anything..
I even hate it when an application DOESN'T have a splashscreen (like firefox or IE), I have to wait and guess if something is happening before the actual application is shown.. A good application that has any loading needed should show a splash/loadingscreen, so a user knows something is happening, best is also to actually have a progressbar/object, or a line which flashes a lot of texts with what it's loading. It might slow the real loading for a bit maybe, but not the perception to the user, as he/she see's something is happening.. The lack of a loadingscreen (and therefore a long waiting time between the actual double click and seeing the first screen) is a big indication of lack of userinteraction knowledge.. ofcourse the best thing would be not having a loadingtime at all, but since you are targeting a large crowd, you have to keep in mind that there are people with slow devices/computer and people with superduperhyperfast devices/computers, you'll keep them both happy, as the slow one actually sees something happening, and the fast ones don't notice it, as it's gone before they blinked their eyes.. so the first line of code in an application that has something to load, is showing the splashscreen, and then go ahead with loading anything..