|
SocialFeatures
Social Aspects that can be incorporated to the experience
Phase-Requirements IntroductionExpectations of users are geared more and more towards a social experience. It also is a valuable aid in building community and should be a good way to aid developers and artists to meet or to get feedback from the users. DetailsThe OS should come standard with a way to send messages (XMPP?) as well as a easy way to get to a IRC chat room. The Package system should have a built in way to rate and review with the owner of a package being able to communicate with those who have left messages. The theming system should allow for data either visually or audio to be cued in from a networked location. Once cued the data will be cached and treated as local until another cue is received. This can be used for overall things the community is interested (countdowns to some release or a group of people can pool together similar wallpapers which get cycled and new ones added) or can be used to keep track of events (Shared calendar with audio/visual notifications for proximity items) The Plugin system should be a last level for developers. The API is the place for hardcore Developers, Plugins should be the place for serious developers who are very focused on a particular area of influence. If possible plugins would be allowed to open functionality that other plugins could leverage. Since we are based on a apt system we can setup dependencies so that a particular plugin or feature would pull in any other plugins that it needs. (Starting a page for Plugins as well as discussion on this aspect) |