Closed Bug 1128101 Opened 8 years ago Closed 8 years ago

[UX] Investigate design for integration of Hello with the Firefox share feature

Categories

(Hello (Loop) :: Client, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED
backlog backlog+

People

(Reporter: RT, Assigned: sevaan)

References

Details

(Whiteboard: [UX])

User Story

Overview:
- Leverage all sharing providers available through the "Firefox share" functionality (we may want to restrict only the ones allowing one on one sharing in the future but we want to start with all of them in order to understand user behavior)
- A single "share" button allows sharing on any social network that the user may be connected to
- Leverage "Firefox share" UX, the assumption is that a share button inside of the conversation window will allow opening the share panel

This bug is for the design of a UX integrating the "Firefox share" feature inside of Hello.

Attachments

(2 files)

      No description provided.
Blocks: 1082944
User Story: (updated)
Assignee: nobody → sfranks
backlog: --- → Fx38+
Shane, is there a way to set a default regarding Facebook share target?
The options are "On your timeline", "On your friend's timeline", "In a group" or "In a private message".
It seems "In a private message" is better suited for Hello and having it as default as opposed to "On your timeline" as it is currently.
Flags: needinfo?(mixedpuppy)
I cant find any documentation showing how to do that with this dialog.  As well, assuming there is an argument that does this, the currently activated users would not have that functionality.
Flags: needinfo?(mixedpuppy)
RT will create the implementation bug - this is still the UX bug.
Rank: 35
Flags: needinfo?(rtestard)
Priority: -- → P3
Whiteboard: [UX]
Blocks: 1132301
Implementation bug created: bug 1132301
No longer blocks: 1132301
Flags: needinfo?(rtestard)
Blocks: 1132301
Notes from a discussion we had today:
- The current implementation of Firefox share in Fx35 forces the user to get on the web to activate Share providers. This will change in Fx36 (and therefore Fx39 which we target for delivery) to opening the "Firefox share" panel and let the user select the share provider he wants to enable
- The suggested design (display of enabled share providers in the conversation window" requires a new API to be implemented on the "Firefox share" side although this seems doable for Fx39
- Different share providers allow different type of content to be shared (Twitter allows only 140 characters for instance) - we need to address this in the requirements.
- Opening the share panel requires it to be in the menu or the toolbar - we need to clarify how to ensure this becomes true for the users who share on Firefox Hello
(In reply to Romain Testard [:RT] from comment #5)
> Notes from a discussion we had today:
> - The current implementation of Firefox share in Fx35 forces the user to get
> on the web to activate Share providers. This will change in Fx36 (and
> therefore Fx39 which we target for delivery) to opening the "Firefox share"
> panel and let the user select the share provider he wants to enable

It wont change in 36, but certainly by 39.
Attached image Share Panel Integration
Attachment #8565567 - Flags: ui-review?(philipp)
Attachment #8565567 - Flags: review?(rtestard)
Attachment #8565567 - Flags: review?(mixedpuppy)
Regarding strings, I believe Facebook can use the same text as the email (except with an image attached). Twitter has a 140-character limit...how about this, pulled from the email text:

Join me for a video conversation using Firefox Hello! <Hello URL>
Flags: needinfo?(matej)
(In reply to Sevaan Franks [:sevaan] from comment #8)
> Regarding strings, I believe Facebook can use the same text as the email
> (except with an image attached). Twitter has a 140-character limit...how
> about this, pulled from the email text:
> 
> Join me for a video conversation using Firefox Hello! <Hello URL>

WFM. Thanks.
Flags: needinfo?(matej)
Thanks Sevaan, looking good!
A few questions/comments:
- If no service has been added yet, open the panel to "add a service" directly from the "share" button
- What if the share icon is not on the menu?
- Where will the share button be placed by default in Fx39?
- Adding the share panel to the toolbar seems to be an expensive action to allow the user to share, why not just adding this to the menu?
- What happens once the user clicks "Add the share panel to my toolbar", does the share panel get added to the toolbar AND the share panel opens?
- Rather than referring to the "share panel", should we rather refer to the "share button"?
- I created bug 1134133 to define what specific text/visual assets get used with what sharing service
(In reply to Romain Testard [:RT] from comment #10)
> Thanks Sevaan, looking good!
> A few questions/comments:
> - If no service has been added yet, open the panel to "add a service"
> directly from the "share" button

Right

> - What if the share icon is not on the menu?

If it is not on the menu or in the toolbar, you get the promotional popup detailed in the attached file.

> - Where will the share button be placed by default in Fx39?

This has not yet been determined.

> - Adding the share panel to the toolbar seems to be an expensive action to
> allow the user to share, why not just adding this to the menu?

My thinking was that the toolbar is more visible. We just showed the user a popup selling them on the feature, so by accepting it, it should be placed somewhere they can see it and use it again in it's proper context (sharing URLs). By just moving it to the menu it still keeps it buried. A user can always customize again after to move it if they want.

> - What happens once the user clicks "Add the share panel to my toolbar",
> does the share panel get added to the toolbar AND the share panel opens?

Yes.

> - Rather than referring to the "share panel", should we rather refer to the
> "share button"?

Sure. I don't think any formal nomenclature has been decided upon. "Share button" works for me! 

> - I created bug 1134133 to define what specific text/visual assets get used
> with what sharing service
Thanks I updated the US on bug 1132301 to reflect this.
Attachment #8565567 - Flags: review?(rtestard) → review+
backlog: Fx38+ → backlog+
Flags: firefox-backlog+
Comment on attachment 8565567 [details]
Share Panel Integration

Yeah, that would work.
What happens if the Hello conversation is in a separate window without a toolbar? Where would the share panel show up in this case?

Also, Sevaan, you should probably talk with Markus and Michael. The share button/panel plays a role in the task continuity work and they might have changes planned (but that doesn't need to block this work for now).
Attachment #8565567 - Flags: ui-review?(philipp) → ui-review+
(In reply to Philipp Sackl [:phlsa] please use needinfo to make me respond from comment #13)
> What happens if the Hello conversation is in a separate window without a
> toolbar? Where would the share panel show up in this case?

Updated the mockup with a note re: this. If window is popped out, the list of services is replaced with the full share panel.

> Also, Sevaan, you should probably talk with Markus and Michael. The share
> button/panel plays a role in the task continuity work and they might have
> changes planned (but that doesn't need to block this work for now).

Flagged them for feedback.
Attachment #8569938 - Flags: feedback?(mmaslaney)
Attachment #8569938 - Flags: feedback?(mjaritz)
Comment on attachment 8569938 [details]
Share Panel Integration (Update #1)

We currently have no changes planed as we are rather exploring possibilities.
We want to extend the functionality of share and bring it closer to bookmarking.
There are some first prototypes by Blake: http://people.mozilla.org/~bwinton/reading-list/
I think including Hello a a part of share, or a possibility to share is a great idea.

I like your compact share menu in the first screen. It takes away some of the somewhat intimidating appearance of the huge share window.
Attachment #8569938 - Flags: feedback?(mjaritz) → feedback+
Attachment #8565567 - Flags: review?(mixedpuppy) → review+
moved up as I hadn't prioritized this high enough in 29.  Sevaan was actively working.
Rank: 35 → 23
Priority: P3 → P2
Rank: 23 → 18
I think this design is final.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Attachment #8569938 - Flags: feedback?(mmaslaney)
You need to log in before you can comment on or make changes to this bug.