I have developed an Android app which plays an audio stream. There are three ways for the user to make the app go away:
- Push the back button on their mobile device.
- Push the close [x] on the top right hand corner.
- Push the home button.
In addition, if the stream is playing, there are also three possible behaviours for both of these close mechanisms:
A. Prompt for the user to decide if they want the stream to stop.
B. Don't prompt, and just stop the stream.
C. Don't prompt, and just carry on playing in the background.
The app currently behaves in the following way:
- (1A) Back button is pushed -> prompt the user for input and then go away.
- (2B) [x] button pushed -> just kill the stream and go away.
- (3C) Home button is pushed -> don't prompt, carry on playing and go away.
I feel like the 1A and 3C behaviours are fairly consistent with the way a user would expect an app to behave. The issue/question is with the 2B [x] behaviour.
My original thinking was for the [x] button to indicate be a much stronger "go away!" intention, where the app immediately complies and doesn't bother with any kind of prompting.
However, I am questioning if this is the best behaviour, since now all three "go away" methods have different behaviours and could be confusing. Now the user has to remember that if they want it to continue, they must push the back button or the home button. I think it would be better to prompt the user when they push [x]. Thus, my question is as follows:
Which is more important?
Going away quickly when the [x] button is pressed, but now the behaviour between all three exit mechanisms is inconsistent.
Always prompting the user on behaviour at the expense of taking longer to close, but now the "go away" behaviours are consistent across the app.