Closed Bug 1088368 Opened 10 years ago Closed 3 years ago

Advertise Send Tab to Device better

Categories

(Firefox for Android Graveyard :: General, defect)

x86
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: antlam, Unassigned)

References

Details

Gemma, we want to teach the user more about the ability to send a tab to their other devices. Right now, the user has to be on a webpage and hit the 3-dot menu, tap the share icon, then find "Send Tab to Devices" (I have a couple builds on my device maybe it says something else).

After this, they're presented with some options like "Send to another device", "Add to reading list", and "Bookmark". We want to advertise this feature a bit more and teach them to use it. 

Current proposals are around using our snippet, timing when that snippet is shown, etc, but we have concerns about relying too much on that little snippet. 
Thoughts?
Flags: needinfo?(gpetrie)
^ See Bug 1007360 for more context
Hey, sorry for the delay here. I wanted to finish up the analysis of the Mirror Tab research I conducted last week since some issues with "Sent Tab to Device" emerged for users. Basically, when asked to try to get content from their Android device onto their TV, nearly all users who encountered the label "Send Tab to Device" thought this was the feature they were looking for. One woman actually went through the entire Sync sign-up process. (See Bug 1088333 for more info.)

I realize that's a larger issue than this bug, but I state it to demonstrate the limited extent of my UR knowledge of how this feature is performing. Regarding snippets in general, I have not conducted user research on how users respond to this call-out over other options, so I don't feel comfortable making that call, but I will look around to see if there is any other research available. 

In the meantime, a few questions:
-Can you also elaborate on your concerns? (I see "bombarding" users as a concern in Bug 1007360)
-Can you elaborate on what, if any, other options you are considering? 
-Are you interested in UR feedback on snippets specifically, or are you more interested in learning about how users respond to contextual hints in general, the appropriate timing, volume, etc?

Thanks!
Flags: needinfo?(gpetrie) → needinfo?(alam)
(In reply to Gemma from comment #2)
> In the meantime, a few questions:
> -Can you also elaborate on your concerns? (I see "bombarding" users as a
> concern in Bug 1007360)

I would mainly be concerned with creating a "contextual snippet" that differs from the one that is normally seen on "Top Sites". Not a huge concern, but just want to make sure if we're creating special case UI, it's for a reason.

> -Can you elaborate on what, if any, other options you are considering? 

Right now, we're just talking about creating a "snippet" that would appear in the "Remote Tabs" panel. I really just wanted to see if this was the best way to do it (in terms of where users would look, etc)

> -Are you interested in UR feedback on snippets specifically, or are you more
> interested in learning about how users respond to contextual hints in
> general, the appropriate timing, volume, etc?

Some general feedback on snippets would be great!
Flags: needinfo?(alam)
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.