Design Team/Proposals/Groups
< Design Team | Proposals
Groups mockup
TODO:
- Get agreement on any of thisĀ :-)
Add buddy to existing Group from Neighbourhood

Buddy palettes would show self tags (tags the buddy added to their own profile) and a new "Add to Group -->" menu showing any groups the user had already created (managing these groups is performed in the Group view). Friends can be considered as a default group provided by the system that you can't delete.
Group view with additional management
Group view with additional management

Clicking the combination box reveals the other Groups already defined, including the default "Friends" group provided by the system. Selecting an entry updates the buddy icons shown on the main canvas for that Group. Clicking the erase (-) toolbar button would raise an alert "Confirm erase: Are you sure you want to permanently erase the '<group_name>' group? (Keep/Erase)". Typing a new string into the combination box would activate the add group (+) toolbar button and disable the (-) button. Typing a new name then clicking (+) would create the group and clear the canvas of previously shown buddies (you'll see none here until you add them from neighborhood).
Journal view showing "Send to --> Group"

Once we have named Groups, the Journal "Send to -->" feature can be extended at some future release cycle to support sending an entry to a whole group. Named Groups could also appear in the Activity "Share with:" menu for quick private collaboration with a number of buddies (each buddy in the Group would receive an Activity invite request).
Former Design Sketches
These images represent some earlier explorations of Groups, of both "open" and "closed" nature. For additional background on groups and their behaviors, please see Design Team/Specifications/Groups. If the above "local group" concept is implemented as a stepping stone to this model, we should be very clear in determining how that transition will happen. It's unclear to me how to illustrate the difference between the two, or how to convert local named groups to mutual open groups down the road. I do, however, see the open and closed groups specified here as more useful than local group names, since the benefits of group creation are enjoyed by all members.

The groups one belongs to appear in the "Start with" and "Send to" menus, making sharing and collaborating with sets of friends easy and efficient. I like Gary's use of the group icon in the menus. In fact, we might assign "arbitrary" colors to groups based on their creator. The group icon we'd use in the UI (in the Journal list, menus, etc.) would be the three dots, with stroke and fill, rather than the circled white zoom level icon.
Subpages