Progress wheel dialog
It works like this:
Progress wheel dialogs can be applied in lots of tasks and contexts. In this wireframe the user is logging in to an application. He first fills in his username and password and hits the log in button.
The log in details need to be authenticated. During this process a progress wheel dialog is shown, meaning the user doesn’t know how much time it will take for the task will be finished.
When the log in process is done, the user enters the app on its opening page, here a dashboard.
A dialog is usually a small window that appears in front of the current activity, making the underlying activity loose its focus. Progress dialogs are mainly used to indicate an app is (down)loading items. If you want to show your users that your app is busy with the activity and making progress, however you cannot define how much progress is being made, a progress wheel dialog can be used.
If you want to show quantified progress, you should apply a progress bar dialog. When you want to show the progress of an event that's running in the background, you should use ongoing status bar notifications.
- The message that an activity is taking place is clear
- \"While processing the user cannot perform any actions in the app.\" This could be good, i.e. authentication required before application use (aw4y)
- User can cancel its whenever want(if implemented that way) (Burak Dede)
- User doesn't have a clue how much time the process will take
- While processing the user cannot perform any actions in the app. He is forced to wait, or jump to an other app
- There is no button to cancel the process that is shown by a progress wheel dialog
- Its not always obvious to user how to cancel dialog (Burak Dede)