Web 2. Session: Comparing Social Platforms 4/23/08 8:30-9:20
Wednesday, April 23, 2008
Innovations on the profile.
Facebook: Vague as always
Bebo: We've always been focussed on engagement. App charts via ratings. Shying away from emphasis on installs. Tangible Metrics. Encourage time spent and retention. Not throttling or sanctioning.
MySpace: Innovating on Home (private) and profile (public). News, Auctions. Early stages. IRC channel for dev community. Taking it slow. Makin data available to developers, Movie and Music data access. Making on site data stores more convenient to use.
Data Portability
Facebook: Intent is to enable user to take data with you wherever you go - both user and developer. Intentionally restrict access to contact information for spam purposes. As industry "our responsibility to work together".
Sixapart: Evolution of mashups into apps, opensocial. Next evolution, not one website inside of another, but two working together.
Google: OpenSocial is intended to be useful on the web in general, not just social network. Extensible, (hi-5). SN can expose additional services and api's. HI-5: Photos and presence.
Google: Facebook creating a new area. Standards can be beneficial because they can establish a market for everybody.
Deals before and after the launch of FB Platform.
MySpace: Open social extensions enable them to choose whenever they need to play along with standards or go their own route.
MySpace: Arrogant to think they can do better than the developers. As we expand music venture, going to make music data available to both internal and external vendors.
SixApart: Too much variation in API's for OpenSocial, photos in Flickr vs. MySpace photos.
Google: Api's for Apps on a platform!
Facebook: There are amazing Verticals that have not ben tapped yet. Sports, Productivity, etc.
SixApart: Our app competes with our own beacon notification.
FaceBook: Distribution is the big mess. Lots of rules to figure out.
Bebo: Building a marketplace. Looking into other verticals. How can apps help us and how can we help them? Partnerships cannot be to narrowly focussed, such as with a single video game company.
Facebook: Reputation system for Apps. User experience. Different types of distro opps depending on how users perceive the apps. Help users understand how to give feedback. Algorithmic as possible as opposed to taking an editorial role.
How are you going to change the mentality o developers to cooperation?
Bebo: Ensuring that viral channels work. Developers will try to game those channels. Promote and reward the most engaging apps. Focus on building a compelling product as opposed to trying to spam users.
MySpace: Lineage of people trying to game the system. App that sends external email to users. Mail spam is not like social spam. Apps getting chatty...
FaceBook: I think that in any system there's arbitrage. Same behavior in any market place or system. Our job to be in service of the user. Some apps do need to send a whole bunch of emails. EX: Causes is doing a positive thing and FB wants to encourage that. Some apps have a low threshold, others need to send a lot of notifications. How do we set rules and create incentives for the developers while maintaining a good user experience?
Google: Open social has a wide set of viral channels available. Each network chooses which channels to utilize. Google likes to se the word "organic" instead of "viral". Channels: Activity Stream and Messages
Facebook: Apps that focus on viral growth grow fast and die fast.
User Experience
Facebook: Apps often viral, but lacking social.
Monetization:
MySpace: Apps need a large install base. Focus on Self-Serve and hyper-targeting. Testing categories in hyper-targeting.
Bebo: Anyone trying to build a marketplace has to think about monetization. How can we ashare data that helps the developer monetize? Over the next year, a lot of cool new developments and innovations.
Facebook: 2008 a big year for monetization. FB working on social commerce. Commerce engine, payments. Fluff Friends, etc using virtual currencies.
Sixapart: MAKE IT EASY FOR THE DEVELOPER! Controlled extensibility. Far too difficult.
Google: BTW, We already have monetization, AdSense and Google Checkout.
Bebo: Downtime? Uh, downtime sucks.
Sixapart: We have FOAF and XFN woo hoo!
Facebook: What does it mean when a user wants to move data around? Should we be threatened? Trying to emphasize "privacy portability" as a way to make "data portability" sound risky.
Sixapart: FB doesn't care about portability, all talk. Not really - all talk about portability is just talk. True portability will come naturally.
Facebook: Vague as always
Bebo: We've always been focussed on engagement. App charts via ratings. Shying away from emphasis on installs. Tangible Metrics. Encourage time spent and retention. Not throttling or sanctioning.
MySpace: Innovating on Home (private) and profile (public). News, Auctions. Early stages. IRC channel for dev community. Taking it slow. Makin data available to developers, Movie and Music data access. Making on site data stores more convenient to use.
Data Portability
Facebook: Intent is to enable user to take data with you wherever you go - both user and developer. Intentionally restrict access to contact information for spam purposes. As industry "our responsibility to work together".
Sixapart: Evolution of mashups into apps, opensocial. Next evolution, not one website inside of another, but two working together.
Google: OpenSocial is intended to be useful on the web in general, not just social network. Extensible, (hi-5). SN can expose additional services and api's. HI-5: Photos and presence.
Google: Facebook creating a new area. Standards can be beneficial because they can establish a market for everybody.
Deals before and after the launch of FB Platform.
MySpace: Open social extensions enable them to choose whenever they need to play along with standards or go their own route.
MySpace: Arrogant to think they can do better than the developers. As we expand music venture, going to make music data available to both internal and external vendors.
SixApart: Too much variation in API's for OpenSocial, photos in Flickr vs. MySpace photos.
Google: Api's for Apps on a platform!
Facebook: There are amazing Verticals that have not ben tapped yet. Sports, Productivity, etc.
SixApart: Our app competes with our own beacon notification.
FaceBook: Distribution is the big mess. Lots of rules to figure out.
Bebo: Building a marketplace. Looking into other verticals. How can apps help us and how can we help them? Partnerships cannot be to narrowly focussed, such as with a single video game company.
Facebook: Reputation system for Apps. User experience. Different types of distro opps depending on how users perceive the apps. Help users understand how to give feedback. Algorithmic as possible as opposed to taking an editorial role.
How are you going to change the mentality o developers to cooperation?
Bebo: Ensuring that viral channels work. Developers will try to game those channels. Promote and reward the most engaging apps. Focus on building a compelling product as opposed to trying to spam users.
MySpace: Lineage of people trying to game the system. App that sends external email to users. Mail spam is not like social spam. Apps getting chatty...
FaceBook: I think that in any system there's arbitrage. Same behavior in any market place or system. Our job to be in service of the user. Some apps do need to send a whole bunch of emails. EX: Causes is doing a positive thing and FB wants to encourage that. Some apps have a low threshold, others need to send a lot of notifications. How do we set rules and create incentives for the developers while maintaining a good user experience?
Google: Open social has a wide set of viral channels available. Each network chooses which channels to utilize. Google likes to se the word "organic" instead of "viral". Channels: Activity Stream and Messages
Facebook: Apps that focus on viral growth grow fast and die fast.
User Experience
Facebook: Apps often viral, but lacking social.
Monetization:
MySpace: Apps need a large install base. Focus on Self-Serve and hyper-targeting. Testing categories in hyper-targeting.
Bebo: Anyone trying to build a marketplace has to think about monetization. How can we ashare data that helps the developer monetize? Over the next year, a lot of cool new developments and innovations.
Facebook: 2008 a big year for monetization. FB working on social commerce. Commerce engine, payments. Fluff Friends, etc using virtual currencies.
Sixapart: MAKE IT EASY FOR THE DEVELOPER! Controlled extensibility. Far too difficult.
Google: BTW, We already have monetization, AdSense and Google Checkout.
Bebo: Downtime? Uh, downtime sucks.
Sixapart: We have FOAF and XFN woo hoo!
Facebook: What does it mean when a user wants to move data around? Should we be threatened? Trying to emphasize "privacy portability" as a way to make "data portability" sound risky.
Sixapart: FB doesn't care about portability, all talk. Not really - all talk about portability is just talk. True portability will come naturally.
0 Comments:
Post a Comment
Links to this post:
Create a Link
<< Home