796791 - [bluetooth] need a vibisibility countdown

Status: RESOLVED DUPLICATE of bug 1121913

(Firefox OS Graveyard :: Gaia::Settings, defect, P4)

Description

[GH to BZ]

[GitHub issue by fabi1cazenave on 2012-09-28T21:49:54Z, https://github.com/mozilla-b2g/gaia/issues/5463]
#5447 sets a two-minute visibility timeout for the Bluetooth. It works fine but it can give the impression that the Bluetooth visibility has a bug.

I suggest using a very thin `<progress>` element at the bottom of the visibility on/off list item to show the elapsed/remaining time.

Comment 1

[GH to BZ]

[GitHub comment by fabi1cazenave on 2012-09-28T21:50:48Z]
/cc @evelynhung

Comment 2

[GH to BZ]

[GitHub comment by evelynhung on 2012-09-29T04:24:52Z]
I don't think progress bar is a proper visual, because it's not something in progress. 
But I agree we need a good visual here, thanks for the issue. :)
@jcarpenter @lco

Comment 3

[GH to BZ]

[GitHub comment by jcarpenter on 2012-10-01T16:20:39Z]
@caseyyee 

Casey is sharing Bluetooth responsibilities with @lco and may have an opinion here.

Comment 4

[Larissa Co [:lco]]

Android has a countdown clock. It's not bad if we want to go this way. It just feels like we are stressing the user out unnecessarily (oh no! I only have 2 minutes to complete this action!). On the flip side, not having a clock can lead the user wondering why their bluetooth keeps toggling back to invisible.

Comment 5

[Casey Yee]

I don't think we need to have a countdown clock necessarily.   I think some kind of indefinite progress indicator will also do.  This way we avoid the unnecessary stress as Larissa has pointed out, but still provide some indication that the device is indeed discoverable.

Comment 6

[Larissa Co [:lco]]

Wouldn't it be cool to have an eye icon that slowly fades as it the device becomes invisible? ;-)

Comment 7

[Peter La]

I really feel for this that we need to show some semblence of how long is remaining, or it will just be confusing (and imo more stressful for the user).

I did a couple of mockups that show this idea.

1) Circular reverse progress bar:
https://www.dropbox.com/s/luhia6pvpgp0wbr/BluetoothVisibilityCounterCircularReverseProgress.png

2) Text timer:
https://www.dropbox.com/s/ig1qoco5tomqi7g/BluetoothVisibilityCounterNumber.png

Please comment on this and let's try to bring this to a consensus as quickly as possible.

Thanks!
Peter

Comment 8

[Evelyn Hung]

I personally like proposal #1, the circular is nice and harmonic. If I have time, I'd like to implement this. (or if someone is interested in this visual, welcome to take it.)

I have another proposal: how about adding a description like 'lasting ~2 minutes' below the 'visible to others'? I think it's much simpler and telling the truth.

Comment 9

[Larissa Co [:lco]]

Thanks for mocking this up, Peter! I like how clean you were able to make it-- that was one of the things I was worried about. I am ok with either design, though I'm probably leaning towards the circular icon because it's easy to grok and it's compact. We need to think about how this affects space when the text (from the language) is long.

Comment 10

[Peter La]

Thanks Evelyn and Larissa for the feedback.

I don't think putting a text description like 'lasting ~2 minutes' is a good idea.  It can be misleading once there is anything less than 2 minutes is left.  If you don't think you have the time to implement the circular countdown meter, then I suggest going with the following idea:

https://www.dropbox.com/s/rgytuyi3rtqtskj/BluetoothVisibilityCounterIcon.png

Basically, just display a little 'time' icon, and fade it.  This should be less work.  We don't necessarily have to fade it either... it could just display solid for the whole 2 minutes, but at least it is not misleading.

If Larissa is ok with this solution, can we go with it Evelyn?

Thanks.

Comment 11

[Larissa Co [:lco]]

Hmm... I don't know if a fading clock is something that users will understand. It just seems like it requires the user to pay attention to notice the different states. What I liked about the circle timer was that it showed parts in relation to the whole. Therefore, at any point in time, the user could glance at it and recognize how much relative time was left. If I had to rank the choices, they would be:

1. circle timer
2. numeric countdown
3. fading clock

Evelyn, what's your estimate on feasibility? If the fading clock is the easiest by far, I'm ok with putting it in for v1. But if it doesn't take that much more effort to do #1 or #2, then I'd prefer one of those.

Comment 12

[Peter La]

Larissa - I agree, good point.  It was originally meant as a easy to implement solution and didn't have the fade.  So we can think of it as just being an icon without fade.  Also, I agree with your ordering of preference.

Evelyn, let us know what you are able to implement.

Comment 13

[David Scravaglieri [:scravag]]

Not a blocker because you can try again.

Comment 14

[Evelyn Hung]

This is a visual hint to let user know when the device visibility will be changed, I think it's important.

Comment 15

[David Scravaglieri [:scravag]]

We would take a patch to solve it.

Comment 16

[Evelyn Hung]

(In reply to GH to BZ from comment #0)
> [GitHub issue by fabi1cazenave on 2012-09-28T21:49:54Z,
> https://github.com/mozilla-b2g/gaia/issues/5463]
> #5447 sets a two-minute visibility timeout for the Bluetooth. It works fine
> but it can give the impression that the Bluetooth visibility has a bug.
>
It really did the impression: bug 816748. :-(

I'd like to raise its importance again, because nobody will work on it if it's not a bb+ issue. It's more like a feature, not UI polish.
Thanks for your time and attention.

Comment 17

[Josh Carpenter [:jcarpenter]]

Does the on/off toggle flip back to "off" once the timer runs down? If so, that would provide some degree of visual feedback for the user.

Comment 18

[David Scravaglieri [:scravag]]

We did the test in triage, the toggle flip back to "off"

Comment 19

[Eric Pang [:epang] UX]

Hi Evelyn, just wanted to check in and see what the status of this bug is.  I tested on a device (2013-03-11) and noticed none of the proposed solutions have been implemented (besides the toggled flipping back to off when the time runs out).

Comment 20

[Evelyn Hung]

Yes, this issue wasn't labeled as a higher priority so it's not included in our schedule. If you think it's very important, please set it leo? to catch someone's attention. Thanks!

Comment 21

[Walter Chen[:ypwalter][:wachen]]

Hi, Arthur, I think partner has modified and finished something in Buri for bluetooth count down. I guess you can reference on their stuffs.

Comment 22

[Arthur Chen [:arthurcc][inactive after 6/30]]

Thanks for the information, Walter!

Comment 23

[Bruce Huang [:bhuang] (inactive)]

Backlogging.