Android: What is the best design choice? Lazy loading or initial wait time?

Question

I was an active fan of lazy loading, but yesterday I talked with another programmer who showed me another application and expressed how glad he was that the waiting time had begun, which the application accepts (more precisely, the Android Marketplace) to load up the list and let it scroll smoothly than lazy loading and making his life miserable ...

Although I can get a lazy load for work using background image loading to make everything feel smooth, I'm still not sure which one is the preferred design methodology ... Any suggestions?

Answer 1

The main component of the user interface design is the response of the user interface. Now, realistically, there will always be a wait time - applications must load, data must be filled, etc. The trick here is to always give user feedback that something is being done, and, of course, not to spend too much time loading screens (I'm looking at you PS1!).

, . , /, ( ). , . " " " , ".

, - . ( ).

Answer 2

. , , :

• .
• .

, , . .

, , . , , . , .