Activity indicators (spinning wheel) and progress bars are very common across many applications.

A new approach I have noticed is when an application shows the containers of the page or content while still loading the actual content. When the content is loaded it fills in the details replacing the empty area. Facebook's iOS app will load the container of a picture, with a big white rectangle, until it loads the actual picture a split second later. There is no activity indicator blocking user interaction.

Are there any articles or research papers that go into more depth on this topic? I have searched the previous posts but I cannot find anything that discusses this progressive loading approach.

2 Answers 2


In general it is accepted in HCI research [1] that the presence of progress indicators enhances the UX of an interface by providing a degree of interactivity, responsiveness, and informativeness to its user. However, it has also been demonstrated that the style or implementation of a progress indicator can have an important impact on the user's enjoyment and perception of an interface [2].

As for your specific question regarding the piecemeal loading of web pages, I believe there are several factors that come into play. If a web page has several components that take a long time to load (or the user is on a less-than ideal connection, i.e., through a smartphone), piecemeal or on-demand loading of page components can have a profound effect on the user's perception of the responsiveness of the interface. On the other hand, I have seen studies that show that heavy use of progress indicators can actually give users the perception that delays are longer than they actually are (this finding was driven by the desire to find out how long to wait before displaying a progress indicator when doing an asynchronous operation, however, so its findings may not be generalizable to this situation).

I could not find any research evaluating this specific technique, however, the software industry seems to be adopting it as a valid approach to designing "heavy" pages. Whether or not such techniques require progress indicators (as in your Facebook app example) remains to be seen but likely depends on the efficiency with which remote content can be received.

[1]: Brad A. Myers. 1985. The importance of percent-done progress indicators for computer-human interfaces. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI '85). ACM, New York, NY, USA, 11-17. DOI=10.1145/317456.317459 http://doi.acm.org/10.1145/317456.317459

[2]: Sumaru Niida, Satoshi Uemura, Hajime Nakamura, and Etsuko Harada. 2011. Field study of a waiting-time filler delivery system. In Proceedings of the 13th International Conference on Human Computer Interaction with Mobile Devices and Services (MobileHCI '11). ACM, New York, NY, USA, 177-180. DOI=10.1145/2037373.2037401 http://doi.acm.org/10.1145/2037373.2037401


Check our this article by NN group http://www.nngroup.com/articles/response-times-3-important-limits/ . It details when to display a progress bar and when not to.

Basically, if the wait time is minimal (less than 1 second), then you can afford not to use a progress bar. Anything more, then the user expects some feedback about the operation taking time.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.