Bug 12360 - List of games: Function of the Back-Arrow unclear. Confirmation Dialogue needed?
: List of games: Function of the Back-Arrow unclear. Confirmation Dialogue needed?
Status: NEW
Product: Miniature
UI
: master
: All All
: Medium normal (vote)
: ---
Assigned To: Uwe Kaminski
: general
:
:
:
:
  Show dependency tree
 
Reported: 2011-08-29 23:13 UTC by Uwe Kaminski
Modified: 2011-08-30 23:11 UTC (History)
2 users (show)

See Also:


Attachments
Implementation of an Dialog to avoid switching back by mistake (1.00 KB, patch)
2011-08-30 10:09 UTC, Uwe Kaminski
Details


Note

You need to log in before you can comment on or make changes to this bug.


Description Uwe Kaminski (reporter) 2011-08-29 23:13:24 UTC
SOFTWARE VERSION: 
master branch (2011-08-29)

EXACT STEPS LEADING TO PROBLEM: 
1. Run Miniature
2. Tap onto "Join as a guest" -> The list of game offers is shown.
3. Tap onto the "Back-arrow" in the left bottom corner

EXPECTED OUTCOME: 
Logging off from the FICS server. To avoid this by mistake there should be a
confirmation dialogue: "You will be disconnected from the game server. Are you
sure?"
Options:
Yes, leave server
No, stay logged in

ACTUAL OUTCOME: 
The initial screen is shown. There is no hint if the user is disconnected from
the server or not.

REPRODUCIBILITY: 
always
Comment 1 Uwe Kaminski (reporter) 2011-08-30 10:09:28 UTC
Created an attachment (id=3408) [details]
Implementation of an Dialog to avoid switching back by mistake

This patch is the solution of this bug IMHO. Please commit if you agree.
Comment 2 Quim Gil 2011-08-30 17:00:18 UTC
I'm not sure if a confirmation dialog is needed? 

- You start out of FICS.
- You login to FICS. A PageStack like effect wrings you to the right / forward.
- You press a 'Back' arrow key pointing to the left.
---> You're out of FICS.

Maybe this is an assumption you won't do the first time, but you're not loosing
much (e.g. no game is interrupted or something) and re-login is simple.

Saving us from this risk by imposing an extra step to everybody (plus extra
strings to translate) seems on overkill to me.

fwiw partially thanks to your feedback I'm trying to save as many 'confirmation
steps' as possible. For instance, I'm thinking on a way to select a game in a
single tap without needing confirmation.

Let me know what do you think about this reasoning. Leaving the report open for
more opinions.
Comment 3 Uwe Kaminski (reporter) 2011-08-30 23:11:34 UTC
(In reply to comment #2)
> I'm not sure if a confirmation dialog is needed? 
> 
> - You start out of FICS.
> - You login to FICS. A PageStack like effect wrings you to the right / forward.
> - You press a 'Back' arrow key pointing to the left.
> ---> You're out of FICS.
> 
> Maybe this is an assumption you won't do the first time, but you're not loosing
> much (e.g. no game is interrupted or something) and re-login is simple.

It's very easy and quick to jump back one screen using the arrow but it may
need some time to log in again. I'm not sure what happen if a user is logging
in again and again very fast. The outcome of tapping the arrow is not clear for
the user but is getting more clear if there is a dialog.

An other problem could be a function which is not available yet: The
possibility to kibitz one or more game. This feature will need a list of
running games (which is a special case of the SeekGame screen). It would be bad
to loose the server connection (all kibitz games will stop). Even if I play a
game it would be great to choose an other one to view. Okay maybe not me but
mikas. :) 

The third problem I see is that in other Screens the back arrow always brings
up a dialog. In the OnlineBoard screen for example a menu appears. But its a
bright menu with it's items on left bottom and not one of these dark looking
dialogs with buttons in the middle of the screen. Maybe both back confirmation
dialogs should be the same visual type.


> Saving us from this risk by imposing an extra step to everybody (plus extra
> strings to translate) seems on overkill to me.
> 
> fwiw partially thanks to your feedback I'm trying to save as many 'confirmation
> steps' as possible. For instance, I'm thinking on a way to select a game in a
> single tap without needing confirmation.

I agree with your general point of view regarding confirmations but they may be
necessary if the consequences are bigger than the user is aware of.

> Let me know what do you think about this reasoning. Leaving the report open for
> more opinions.

That never is bad :)