Just how fast is too fast when it comes to web requests?

Re:Just how fast is too fast when it comes to web requests? by jobigoud on Wednesday November 13, 2019 @08:52AM (#21523937)

In a hobby desktop app, I show a splash screen before the UI is fully loaded. After optimizing startup time, it's now at a point where a hot start is very fast, less than 300 ms, to the point that you can't really read anything on the splash screen. Cold start still takes a second or so.

Is there a best practice here? At which point do you stop showing a splash screen? I've seen applications where the splash screen lingers even after the UI is loaded, which seems weird to me and gets in the way of getting things done.

[ Parent | on HN ]

Re:Just how fast is too fast when it comes to web requests? by KarlTheCool on Wednesday November 13, 2019 @03:19PM (#21529024)

Probably a skeleton screen would be better. Show an empty version of the usual ui but with blocky placeholders as stuff loads in.

https://uxdesign.cc/what-you-should-know-about-skeleton-scre...

[ Parent | on HN ]

Re:Just how fast is too fast when it comes to web requests? by jobigoud on Wednesday November 13, 2019 @06:19PM (#21530884)

Thank you very much for introducing me to this concept! This gives me some ideas on how to organize the loading. There is definitely stuff I do in the background of the splash screen that could be done later, after a simplified version of the main window is loaded.

[ Parent | on HN ]

Re:Just how fast is too fast when it comes to web requests? by timw4mail on Wednesday November 13, 2019 @09:52AM (#21524744)

Don't show a splash screen.

[ Parent | on HN ]