Pull-to-refresh in business apps: when and how to use it
Short answer: Pull-to-refresh is the gesture where people drag a list down to load the latest items. It suits screens with a chronological feed that changes often, such as orders, messages, bookings or job lists. Use the platform's own control so it looks and behaves as expected, always end the spinner when the update finishes or fails, give people a visible refresh option as well, and don't rely on the gesture as the only way new data arrives.
Where pull-to-refresh fits
The gesture works when three things are true:
- The screen is a scrolling list, usually newest first.
- The content changes in ways the user cares about, like new orders coming into a café's order screen or new job assignments for a tradesperson.
- People want to check for updates on demand.
It's less useful, and sometimes confusing, on:
- Static screens like settings or a product page.
- Forms, where a stray downward drag shouldn't throw away what someone typed.
- Maps and canvases, where a downward drag means "move the view".
- Screens that already update live, where a refresh does nothing visible.
Use the platform control
Both mobile platforms provide a standard component. Using it gives you the expected visuals, physics and accessibility hooks for free.
Android. Google's guide describes the swipe-to-refresh pattern as implemented by the SwipeRefreshLayout widget, which detects the vertical swipe, shows a progress indicator and calls back into your app. You add it as the parent of a list. For Jetpack Compose apps, Google provides a pull-to-refresh component documented separately.
iOS. Apple's UIRefreshControl is described as a standard control that can start the refreshing of a scroll view's contents. You attach it to a scroll view or table, respond to its value-changed event by updating your content, and Apple's documentation is explicit that you call endRefreshing() when you're done. There are also beginRefreshing() and an isRefreshing property for managing the state.
Cross-platform frameworks usually wrap these native controls. Prefer the wrapper over a custom-built gesture.
Always end the refresh
The most common bug is a spinner that never stops. It happens when:
- The network request fails and the error path forgets to stop the indicator.
- The request times out with no handling.
- The user leaves the screen mid-refresh and returns.
Make sure every outcome, success, error, cancellation or timeout, ends the refresh state. On iOS that's endRefreshing(); on Android you set the refreshing state back to false.
Tell people what happened
A spinner that disappears with no change leaves people unsure whether anything happened.
- New items: insert them at the top and, if the user had scrolled, a small "3 new orders" marker helps.
- Nothing new: a brief "You're up to date" message, or an updated "Last updated 2:14 pm" line.
- Failure: a clear, short message such as "Couldn't refresh. Check your connection." Keep the existing list on screen rather than blanking it.
Don't make it the only way in
Google's guide points out an important gap: some users can't perform swipe gestures. It shows how to add a refresh action to the app bar's overflow menu, so people using external devices, such as a keyboard or switch access, can trigger the update.
That's good practice on both platforms:
- Add a refresh button or menu item on screens where freshness matters.
- Make sure screen reader users can reach it.
- Consider automatic updates when the screen opens or the app returns to the foreground, so people don't have to remember to refresh at all.
Think about the data, not just the gesture
Pull-to-refresh is the visible part. Behind it:
- Fetch only what's new where your API allows it, rather than reloading the whole list.
- Avoid hammering the server. Ignore a second pull while a refresh is running.
- Keep scroll position sensible. If someone pulls while reading the middle of a list, don't jump them to the top unexpectedly.
- Cache the last result so the screen shows something useful instantly, then refreshes.
For screens where updates truly matter in real time, such as a kitchen order screen, push updates or regular background refresh may serve staff better than relying on them to pull.
Test it the way staff use it
Try the gesture on a slow connection, with the network switched off, and while the app is still loading its first screen. Ask a colleague who has never used the app to refresh a list without instructions; if they hesitate, the visible button matters even more. Repeat the checks after each release.
Pull-to-refresh on the web
Mobile browsers have their own pull-to-refresh that reloads the whole page. If your web app has its own refresh behaviour or a scrolling panel, the CSS overscroll-behavior property controls what happens when scrolling reaches the edge of a scroll container, which can stop the browser's gesture from interfering. Use it carefully: disabling the browser's reload everywhere can confuse people who rely on it.
A worked example
A hypothetical Limerick courier firm's driver app shows assigned deliveries. Drivers pull to refresh, but on patchy coverage the spinner often spins forever, so they restart the app. The developers make sure every network outcome stops the indicator, show "Last updated" under the header, keep the old list visible on failure with a short retry message, and add a refresh button to the toolbar. The app also refreshes automatically when it returns to the foreground, so drivers see new jobs without remembering to pull.
FAQ
Should the newest items be at the top?
For pull-to-refresh, yes. The gesture pulls from the top, so new items should appear there.
Is pull-to-refresh needed if the app updates automatically?
Not always, but many people expect it on list screens. If you keep it, make sure it really fetches fresh data.
Can I customise the spinner?
You can usually change colours to match your brand. Big custom animations can feel slow; keep them short.
Does pull-to-refresh work with screen readers?
The gesture itself can be hard to perform, which is why a visible refresh action matters.
If your app's refresh behaviour feels unreliable or confusing, tell us which screens it's on and we'll suggest fixes.