User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In recent work, I came across a problem when designing a loading page for an APP. Other coworkers suggest adding a cancel button on the loading page so that users can cancel loading when they don't want to wait(2 in the pic). But in my opinion, even when loading large contents, user still don't need cancel button in the loading page(1 in the pic). IF the loading can't be done because of network, after certain seconds we can tell the user to try again or cancel(3 in the pic). what do you guys think?

enter image description here

share|improve this question
up vote 5 down vote accepted

You should never add functionality that the user doesn't need / isn't going to use, as it adds complexity and increases maintenance. So let's look at whether a cancel button adds value to your application.

  • During loading, is the device stuck on the loading page, or can the user switch to another application?
  • Does the loading operation use up device resources such that it might impair other functionality (other applications).
  • Is any of the functionality in the application usable if your loading operation fails / is canceled?

The user will require an option to cancel if

  • they are stuck looking at the loading page until it times out, with no option to go do something else / switch application.
  • canceling the loading operation will free up resources needed elsewhere.
  • there is other functionality in the app that they want to get at quickly, which doesn't require this loading operation to complete.
share|improve this answer
Don't think that 'free up resources' is a point here. It seems to be a technical problem users must be unaware of. – alexeypegov Jun 13 '14 at 9:19
@alexeypegov it might not be pertinent for your specific use case, but as general advice it could be useful for someone else reading this. Imagine a phone app that acquired the camera for a video call, and then locked access to it while waiting ages to connect to a remote server. The developer should think about how to release this resource if something goes wrong. – Franchesca Jun 13 '14 at 9:55
especially in a case you're describing: there should be a timeout before an app will cancel the waiting operation automatically rather than a 'cancel' button to let user do it. I mean 'cancel' could be here, but for other reasons (I could change my mind and cancel the call). – alexeypegov Jun 13 '14 at 11:19

I agree that cancelling the loading of the content of a page seems useless if the users stay on the page. However, load times can be very frustrating if the connection is bad and being able to go back to the previous page/view seems logic. (Mobile) browser enable the user to go back one page/view. What a frustrating timespan is, differs form user to user. Jakob Nielsen provides some guidelines:

Maybe, instead of cancelling the load, provide the user with a back-button. This way, he can escape the loading-screen when it's taking too long without ending up with a useless screen.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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