Finally, nice use of animation: Using animation is a bit risky. You must consider the delays and the frequency of use of the app. (I will talk about these two titles in the rest of the article) The Netflix splash screen is a good example of the use of animation.
Considering the example of Netflix; Actually, Netflix’s splash screen contains animation that causes a long delay. So why doesn’t it bother us? Would you be bothered if the same delay was on WhatsApp? (or whatever chat app you are using)
Sum up: When you enter the messaging application, what you want to do is simple; checking messages and writing messages if necessary. Then you are done with that app. You get a message again and you go back into the same loop. You don’t want to wait for a long animation for a short job that will take seconds. Especially if you use the app frequently, these animations become unbearable.
If the time you spend in the app is too long (does not end in seconds) when you enter the app, the animation becomes bearable and we even like it. I guess there is no one entering Netflix for 30 seconds. This is why Netflix animation is not unbearable.
So it totally depends on the purpose of using the app. Let’s do a quick test: Just enter Netflix to find out the last content you watched and then exit right away. Netflix animation will be unbearable if interaction with the app is short.
In an application we use frequently, the splash screen is much more important than we think. Every time the user enters the application, the start page appears first. This is partly related to the usage purpose, as I said. The start page can be a little annoying when there is an error in the background, the user’s internet speed is low, or the user’s phone is slow. Although we try to solve every problem, we cannot solve some user-related problems (such as a slow phone) The important point here is; the start page should be noticed but not disturbing. My favorite splash screen; Twitter.
When we think about it, it immediately comes to our minds, so we notice the animation, but the animation does not cause a delay.
We shouldn’t confuse the splash screen with the loading of the app’s interface. The splash screen causes delays due to the app itself, and the delay of the front face may be due to internet speed or content.
We should not wait for delays due to the loading of the app’s content on the splash screen. If we wait for these delays on the splash screen, the user will think there is a mistake.
After the splash screen, we can wait for the content to load using the skeleton page. Thus, the user does not wait on the splash screen and sees the loading process with the skeleton page. User experience is better as the process can be followed.