763816 - Implement Starred Contacts to Promote Important Contacts, Hide Others

Status: RESOLVED INVALID

(Firefox Graveyard :: SocialAPI, defect)

Description

[Jennifer Morrow [:Boriss] (UX)]

User privacy and control are two important goals for this project.  As discussed in Bug 763806, a user's contacts can themselves constitute highly personal data, which users of the Facebook sidebar may not want to be visible at all times.  Even if users do not mind their contacts being visible, it's likely that of all their Facebook friends, there's probably only a handful they have chat conversations with regularly.  This brings up another problem with a list of contacts: sorting first by status and then by name means that finding a common contact requires scrolling through an often long list.

Providing a way to narrow the list of visible contacts to just a few key contacts solves both the privacy and focus concerns.  The mockups below outline how it would work.  The user would start by starring contacts which are most important to them.  These contacts would jump to the top of their contact list.  Users could stop there and simply have much easier access to the people they talk with most.  If they wish to hide the other contacts, for privacy or for focus, a link to do so appears after the first contact has been starred.

Comment 1

[Jennifer Morrow [:Boriss] (UX)]

Attachment: Mockup: Starred contacts used for contact promotion and progressive disclosure

Comment 2

[Shane Caraveo (:mixedpuppy)]

this seems like the wrong attachment.

Comment 3

[Jennifer Morrow [:Boriss] (UX)]

Attachment: Mockup: Starred contacts used for contact promotion and progressive disclosure (

(fixed)

Comment 4

[Mark Hammond [:markh] [:mhammond]]

This is currently out of our control and would need to be implemented completely by the provider.

Comment 5

[Shane Caraveo (:mixedpuppy)]

I'm going to second Marks last comment, this seems like provider functionality and not something controllable by us.

Comment 6

[Shane Caraveo (:mixedpuppy)]

This is really provider content functionality that we dont have control over, so I'm going to close this.