A habit born in Tweetie
Loren Brichter introduced pull-to-refresh in Tweetie and later patented it (Brichter, 2013). It turned the downward thumb motion users already made at the top of a list into a refresh command, removing the need for a button. It became standard in feed apps, and Android formalised it as swipe to refresh (Google, n.d.).
Threshold, haptics and indicators
Good implementations give three stages of feedback: the indicator follows the drag, a signal shows when release will refresh and loading appears after release. Light haptic feedback at the threshold lets fingers feel the state. React within 0.1 s (Card et al., 1991) and show progress beyond about 1 s (Miller, 1968; Myers, 1985); Nah (2004) found feedback extends tolerable waits. Pairing with skeleton screens improves perceived speed (Harrison et al., 2007).
When to use it and what to pair it with
It suits newest-first feeds, inboxes and notification lists, but clashes where dragging down means something else, such as maps or editors. Combined with infinite scroll it yields a clear 'new above, old below' structure. As a hidden gesture it needs an alternative such as a refresh button for desktop and accessibility users, and should report 'You're up to date' when nothing is new.
FAQ
- Should the web use pull-to-refresh?
- Mobile browsers have their own refresh gesture, so buttons or auto-update notices are safer.
- What if there is no new content?
- Show loading briefly, then a message such as 'You're up to date'.
Sources reviewed: 2026-10-27
References
- Brichter, L. (2013). User interface mechanics (U.S. Patent No. 8,448,084). U.S. Patent and Trademark Office. Loren Brichter's patent behind pull-to-refresh.
- Google. (n.d.). Swipe to refresh. Material Design. Android swipe-to-refresh indicator and behaviour rules.
- Myers, B. A. (1985). The importance of percent-done progress indicators for computer-human interfaces. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 11–17). ACM. Progress indicators make waiting more tolerable.
- Miller, R. B. (1968). Response time in man-computer conversational transactions. In Proceedings of the December 9–11, 1968, Fall Joint Computer Conference, Part I (pp. 267–277). ACM. First systematised response-time thresholds.
- Card, S. K., Robertson, G. G., & Mackinlay, J. D. (1991). The information visualizer, an information workspace. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 181–186). ACM. Proposes 0.1 s, 1 s and 10 s response limits.
- Nah, F. F.-H. (2004). A study on tolerable waiting time: How long are Web users willing to wait? Behaviour & Information Technology, 23(3), 153–163. Users wait longer when given feedback.
- Harrison, C., Amento, B., Kuznetsov, S., & Bell, R. (2007). Rethinking the progress bar. In Proceedings of the 20th Annual ACM Symposium on User Interface Software and Technology (pp. 115–118). ACM. Animation changes perceived waiting time.