Progress Indicator in Mobile UX Design
Visibility of system status is one of the most important rules of UI design. The goal behind this rule is pretty obvious — to minimize user tension you should provide feedback to the user about what is happening with the app within a reasonable amount of time. Don’t keep the users guessing — tell the user what’s happening. And one of the most common forms of such feedback is a progress indicator.
Good Interaction Design Provides Feedback
While instant app’s response is the best, there are simply times when your app are not able to comply with the guidelines for speed. Delays are usually caused by slow loading times and latency issues. For such cases, you must reassure the users that the app is working on their request and that actual progress is being made.
What is A Good Progress Indicator?
Good progress indicator always give some type of immediate feedback. They notify users that the app needs more time to process the user action, and tell (approximately) how much time it will take. They have two main advantages:
Reduce user’s uncertainty (app reassures the user that it’s working).
Offer a reason to wait and reduce users’ perception of time (app gives the user something to look at while waiting. Thus, makes users pay less attention to the wait itself).
A user’s wait time begins the moment when she taps the screen (initiates an action). Immediately, the system should give some visual feedback to communicate that it has received the request.
Types of Indicators
Progress indicator could be determinate or indeterminate:
When indicators are determinate they indicate how long an operation will take when the percentage complete is detectable.
When indicators are indeterminate they request that the user waits while something finishes when it’s not necessary to indicate how long it will take.
Showing an animated graphic on loop offers feedback that the system is working, but usually, doesn’t give enough information about how long the user will have to wait. As a general rule, you should use looped animation only for fast actions (2–10 seconds). Making the user stare at a spinning wheel longer can increase bounce rates.
Default loading icons (like the iOS spinner of gray lines radiating from a central point) tend to have negative connotations. They serve a variety of operating system functions, indicating the status of everything from device boot to problems connecting to network or loading a data. Because of that, people don’t’ like to see only a loading spinner with no indication of progress or time.
Looped Animation Integration
You can integrate looped animation with existing controls, especially buttons. For Android applications, a circular loader may be integrated with a floating action button. The thought process here is to confirm that the submission was complete not necessarily the progress. That is shown through the completion of the circle.
System or Custom Looped Animation
Facebook app has very interesting experience with looped animation. Rusty Mitchell highlighted this moment when he talked about a Facebook loading indicator: “When the users were presented with a custom loading animation in the Facebook iOS app (left) they blamed the app for the delay. But when users were shown the iOS system spinner (right), they were more likely to blame the system itself.”
A determinate linear progress indicator should always fill from 0% to 100% and never decrease in value. For multiple operations happening in sequence, you should use the indicator to represent the progress as a whole, and not each individual operation.
Uncertain waits are longer than known, finite waits. Percent-done progress indicators are the most informative type of wait-animation feedback. They show the current progress, how much has already been accomplished, and how much is left. A percent-done indicator makes users understand how fast the action is being processed.
Provide a General Time Estimate
Don’t try to be exact, a simple, “This might take a minute” can be enough to inform the user and encourage them to wait it out.
Progress bars tell users how long an action is taking, but they’re not always correct. You can disguise small delays in your progress bar by starting the progressive animation slower and allow it to move faster as it approaches the end. The progress bar should never stop, otherwise, users will think the app froze.
Instead of showing a percentage number, consider showing the number of steps. Users might not know how long each step lasts, but knowing the number of steps at least helps them form an estimate.
You should always try to make the wait more pleasant if you can’t shorten the line. And wait-time is a right time for skeleton screens (a.k.a temporary information containers). Skeleton screens are another way to focus on progress instead of wait times. A skeleton screen is essentially a blank version of a page into which information is gradually loaded. Such action creates the sense that things are happening immediately as information is incrementally displayed on the screen.
Medium uses this trick, showing a simple wireframe as a placeholder, while the actual content loads. With such a screen, the focus is on content being loaded not the fact that it’s loading.
Don’t Use Static Progress Indicator
This group of indicators is represented by not moving image or text like “Loading…” or “Please wait…” to indicate that the request has been received. While any feedback is better than none, static indicators don’t offer enough information about what is happening and should be replaced with a more meaningful type of indicator.
One Last Thing
To ensure people don’t get bored while waiting for something to happen, offer them some distraction. This can be something fun, something unexpected or anything else that catches your users’ attention long enough for your app to load. Fine animations can distract your visitors and make them ignore long loading times.