Firefox Social Integration: Difference between revisions

m
no edit summary
mNo edit summary
mNo edit summary
Line 18: Line 18:
The first generation of integrating the social experience into Firefox will consist of four touch points.
The first generation of integrating the social experience into Firefox will consist of four touch points.


* Integration of persistent social notifications into the Firefox toolbar.
# Integration of persistent social notifications into the Firefox toolbar.
* Integration of news feeds, tickers, buddy lists, etc., into a Firefox sidebar.
# Integration of news feeds, tickers, buddy lists, etc., into a Firefox sidebar.
* Integration of chat, voice, video, etc. into docked or floating window.
# Integration of chat, voice, video, etc. into docked or floating window.
* Integration of a share/recommend service in the Firefox toolbar.
# Integration of a share/recommend service in the Firefox toolbar.


With these touch points, users will be able to carry their social presence and tools with them, outside of confines of specific social websites. No longer will users need to be visiting a social provider to share or recommend something within that service, nor will they have to navigate the NASCAR-like mess of social widgets accompanying so much Web content. Users will be able to chat and get updates of various kinds from where ever they happen to be on the Web.  
With these touch points, users will be able to carry their social presence and tools with them, outside of confines of specific social websites. No longer will users need to be visiting a social provider to share or recommend something within that service, nor will they have to navigate the NASCAR-like mess of social widgets accompanying so much Web content. Users will be able to chat and get updates of various kinds from where ever they happen to be on the Web.  
Line 36: Line 36:
* A Google+ user wants to quickly open a chat without chasing down her buried Google+ tab in Firefox. She clicks her buddy's name in the Firefox social sidebar and it pops out a chat Window.  
* A Google+ user wants to quickly open a chat without chasing down her buried Google+ tab in Firefox. She clicks her buddy's name in the Firefox social sidebar and it pops out a chat Window.  


A Facebook user, just about to hit the 1,000 friends mark doesn't want to miss that incoming friend request. Because he's got Firefox's new social features, he'll get a notification in his Firefox toolbar when any new friend requests, new messages, or notifications arrive.
* A Facebook user, just about to hit the 1,000 friends mark doesn't want to miss that incoming friend request. Because he's got Firefox's new social features, he'll get a notification in his Firefox toolbar when any new friend requests, new messages, or notifications arrive.
|Feature dependencies=This feature depends on:
|Feature dependencies=This feature depends on:


1. The Social API back-end implementation  
# The Social API back-end implementation  
2. UR and UX work to test and design the experience for discovery and enabling social features, each of the 4 social touch points, disabling the social feature, and switching between social providers.
# UR and UX work to test and design the experience for discovery and enabling social features, each of the 4 social touch points, disabling the social feature, and switching between social providers.
3. Labs and Firefox engineers to implement the front-end of the Social API
# Labs and Firefox engineers to implement the front-end of the Social API
4. Social providers to offer up an Open Web Application Manifest - which contains the name, icon, and service data needed for the browser to communicate with the web property.
# Social providers to offer up an Open Web Application Manifest - which contains the name, icon, and service data needed for the browser to communicate with the web property.
|Feature non-goals=Mixing and matching different parts from different social providers is a non-goal. Users must be able to switch between providers, but it is not required that users be able to display touch points from multiple providers simultaneously.
|Feature non-goals=Mixing and matching different parts from different social providers is a non-goal. Users must be able to switch between providers, but it is not required that users be able to display touch points from multiple providers simultaneously.
|Feature functional spec=The bulk of the functional spec is described at the [https://wiki.mozilla.org/Labs/SocialAPI Social API doc] and the newsgroup post [groups.google.com/group/mozilla.dev.apps.firefox/browse_thread/thread/1e4048b16c7a6705/7e392549d34e6c62  
|Feature functional spec=The bulk of the functional spec is described at the [https://wiki.mozilla.org/Labs/SocialAPI Social API doc] and the newsgroup post [groups.google.com/group/mozilla.dev.apps.firefox/browse_thread/thread/1e4048b16c7a6705/7e392549d34e6c62  
Proposing some social features for Firefox]
Proposing some social features for Firefox]
|Feature implementation plan=The initial implementation will be delivered as a bundled add-on. Eventually the Social API back-end and front-end will be built-in.  
|Feature implementation plan=The initial implementation will be delivered as a bundled add-on. Eventually the Social API back-end and front-end will be built-in.
}}
}}
{{FeatureInfo
{{FeatureInfo
Confirmed users, Bureaucrats and Sysops emeriti
2,974

edits