Closed Bug 1183538 Opened 7 years ago Closed 7 years ago
Bounce contextual hint icon in URL bar
In bug 1011712 (and now bug 1177612 as well), there's a bounce animation to the icon that draws more attention to this toolbar tip. Talking to Martyn, it sounds simple enough. But I wouldn't block on it so I'm filing this to track that bounce work separately. It'd definitely be a nice complement to the design.
OS: Unspecified → Android
Hardware: Unspecified → All
I find that bounce animations are rarely ever noticed. I don't see any benefit to adding one. If you want to get someone's attention, do it explicitly.
Build to try: https://dl.dropboxusercontent.com/u/7163922/1183538.apk
I tried the build. The bounce itself seems to function well enough on my galaxy nexus. 1. Do we expect the bounce to happen for every tracking pageload? That could very well be *every* pageload. 2. I actually found the "Tracking Protection enabled" hint to be the part I really dislike. 3. The contrast of the TP shield on the Private Browsing color scheme is poor. The TP shield should "pop" more. We can't expect the bounce to be the only way for people to notice the shield. I believe using the bounce for Tracking Protection means we can't use the bounce for Reader or any other icon in the URLBar. Are we ready for that?
(In reply to Mark Finkle (:mfinkle) from comment #3) > I tried the build. The bounce itself seems to function well enough on my > galaxy nexus. > > 1. Do we expect the bounce to happen for every tracking pageload? That could > very well be *every* pageload. Right now, yes. > 2. I actually found the "Tracking Protection enabled" hint to be the part I > really dislike. Good question, we can discuss this more in bug 1177612 since this is more about the bounce. But, I did toss around the idea of disabling this hint/tip once the user opens the doorhanger. Essentially taking a page from the book of progressive disclosure techniques. > 3. The contrast of the TP shield on the Private Browsing color scheme is > poor. The TP shield should "pop" more. Martyn is using the old icons here, Chenxia is working on the patch that updates them. After that, it should be white like the mock in bug 1177612. > We can't expect the bounce to be the > only way for people to notice the shield. > > I believe using the bounce for Tracking Protection means we can't use the > bounce for Reader or any other icon in the URLBar. Are we ready for that? Why not? If this is our format for contextual tips by driving attention to certain icons in our toolbar, we can re-use this UX for other icons too. In a more general sense, one might call this a "notification UI" I'm fine if this raises issues of whether or not we actually NEED to make a big deal about this shield icon in the URL bar. In light of all the attention that Desktop and Marketing will be bringing to it, I'm not sure we still need to anymore. But for those looking it's a nice indicator that can't hurt since it doesn't even get in the way of those people NOT looking. If we're strictly talking UX here, I think this level of boldness is the most that we should really consider for something like this. The feature works well, and it's not vital that a user touches this button. So, that urgency/priority is reflected in the design - I am fully aware that it's subtle. These "nice-to-know" tips shouldn't be smacking you over the head every time. We want to offer users a way to notice it (they will be coming in with other context too, maybe even looking for it), but we also want to not annoy those who are fine with never opening that doorhanger. That being said, we can test this first as well if we choose to. I'm not married to it but it does provide value, some whimsy, and all while being subtle about it.
This one has just the bounce: https://dl.dropboxusercontent.com/u/7163922/1183538-2.apk
Closing this cause we changed the hint UI/UX.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.