RockYou at Girls in Tech Developer Forum
Upcoming SlideShare
Loading in...5

RockYou at Girls in Tech Developer Forum



RockYou's Raymond Chan gave an informative presentation about OpenSocial at the Girls in Tech Developer Summit November 19, 2008 in San Francisco. Raymond gave a short history of OpenSocial and a lot ...

RockYou's Raymond Chan gave an informative presentation about OpenSocial at the Girls in Tech Developer Summit November 19, 2008 in San Francisco. Raymond gave a short history of OpenSocial and a lot of detailed information on coding for OpenSocial.



Total Views
Views on SlideShare
Embed Views



1 Embed 1 1



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

RockYou at Girls in Tech Developer Forum RockYou at Girls in Tech Developer Forum Presentation Transcript

  • It's an OpenSocial Generation A year’s worth of growth, tips, and tricks Raymond Chan - November 19, 2008
  • What is RockYou?
    • Mission – “To engage the world through social applications”
    • Leading developer across all major social networks and platforms
      • MySpace, Facebook, hi5, orkut, Friendster, Bebo, Xiaonei…
    • Large Social Application Reach (excluding profile widgets)
      • Over 90+ million uniques (monthly)
    • RockYou! Team
      • ~80 employees across engineering, product, business development and sales
  • Overview
    • OpenSocial turns one
      • Reviewing a year of enormous growth
    • What is OpenSocial?
      • Overview of the community process
      • Example applications
      • Coding a simple “Hello World” app
    • Developer tips and lessons learned
      • OpenSocial cross-container tips
      • Using analytics to scale – a brief overview of RYStatz
  • What’s so interesting about OpenSocial?
  • What’s so interesting about OpenSocial? Later that year…
  • Taken from OpenSocial “State of the Union” presentation
  • Taken from OpenSocial “State of the Union” presentation
  • A Year of Enormous Growth
    • A resounding success across the OpenSocial ecosystem
      • 315m+ app installs
      • 85m+ daily canvas views
    • RockYou’s Success
      • Launched a portfolio of applications: self expression, communication / messaging, dating, virtual pets
      • Installed over 55m times
      • Material to driving RockYou’s global reach of over 90m monthly users
  • What is OpenSocial?
    • It’s a specification
      • Set of standards for sharing social data and building social applications on the web
      • Defines a set of social APIs and standards
      • Built upon open standards, and utilizes open-source philosophies
    • It’s a community
      • Containers (social sites), application developers, anybody who is interested
      • Open-source implementations (Apache Shindig)
      • The OpenSocial Foundation
  • Exercising the Open Source Model
    • “ The OpenSocial Specification is constantly evolving.  The basic idea behind our process is to treat the spec like an open source software project, following some basic tenets from the Apache Software Foundation:
      • Participation is open to anyone
      • Decisions are made on the spec list (not behind closed doors)
      • All proceedings are captured in a public archive
      • Individuals represent themselves, not companies ”
    • So what can we build with OpenSocial?
  • Application Spotlight – Super Pets!
    • Highly-engaging virtual pets – users adopt and customize pets, then accessorize them and participate in casual and competitive gaming
  • Application Spotlight – Super Pets!
    • Pet customizations / accessories
    • Virtual Currency / Digital Economy
    • Battling / Casual Gaming
  • Application Spotlight – Emote
    • RockYou’s most widely-distributed self expression application
  • Writing a social “Hello World” app
    • Easy to get started
      • Basic apps composed of HTML + javascript
      • Some containers do not even require hosting (just paste in the code)
    • Basic concepts
      • Application gadget XML
      • Views – profile, canvas
  • Example Gadget XML
    • <?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; ?>
    • <Module>
    • <ModulePrefs
    • title=&quot;Hello World!&quot;
    • author_email=&quot;;>
    • <Require feature=&quot;opensocial-0.8&quot; />
    • </ModulePrefs>
    • <Content type=&quot;html&quot; view=&quot;profile&quot;>
    • <![CDATA[
    • Hello, Profile!
    • ]]>
    • </Content>
    • <Content type=&quot;html&quot; view=&quot;canvas&quot;>
    • <![CDATA[
    • Hello, Canvas!
    • ]]>
    • </Content>
    • </Module>
  • ModulePrefs
    • <ModulePrefs
    • title =&quot; Hello World! &quot;
    • author_email =&quot; [email_address] &quot;>
    • <Require feature =&quot; opensocial-0.8 &quot; />
    • </ModulePrefs>
  • Content element per view
    • <Content type =&quot; html &quot; view =&quot; profile &quot;>
    • <![CDATA[
    • <!–- add html and javascript here, as if this were a body section of a web page -->
    • ]]>
    • </Content>
  • Making “Hello World!” a bit more social
    • <script type=&quot;text/javascript&quot;>
    • function request() {
    • var idspec = opensocial.newIdSpec({ &quot;userId&quot; : &quot;OWNER&quot;, &quot;groupId&quot; : &quot;FRIENDS&quot; });
    • var req = opensocial.newDataRequest();
    • req.add(req.newFetchPersonRequest(opensocial.IdSpec.PersonId.OWNER), &quot;get_owner&quot;);
    • req.add(req.newFetchPeopleRequest(idspec), &quot;get_friends&quot;);
    • req.send(response);
    • };
    • function response(dataResponse) {
    • var owner = dataResponse.get('get_owner').getData();
    • var friends = dataResponse.get('get_friends').getData();
    • var html = 'Friends of ' + owner.getDisplayName();
    • html += ':<br><ul>';
    • friends.each(function(person) {
    • html += '<li>' + person.getDisplayName() + '</li>';
    • });
    • html += '</ul>';
    • document.getElementById('message').innerHTML = html;
    • };
    • // Execute the request function when the application is finished loading.
    • gadgets.util.registerOnLoadHandler(request);
    • </script>
    • <div id=&quot;message&quot;> </div>
    From OpenSocial Developer’s Guide
  • Developer Tips and Lessons Learned
    • OpenSocial == Cross-container development
    • Importance of messaging in social apps
    • Dealing with scale
    • Importance of effective analytics for success
  • Cross-Container Development Tips
    • Design flexible layouts to accommodate different view sizes
    • Gracefully handle differences in how containers handle user information
      • Default fields, querying by user ids (0.7), page sizes / ordering
    • Take time to understand how messaging channels are implemented on different containers
      • User experience varies greatly site to site
      • Wide range of user preferences across social networks
  • Cross-Container Development Tips
    • OpenSocial applications have proven to be portable, even to Facebook
    • Canvas pages shared between OpenSocial and Facebook
      • Use common-sense encapsulation and abstraction
    • Facebook iframe application using XFBML/FBJS
  • Scaling social apps
    • Good problem to have, bad problem to deal with…
    Facebook platform launch
  • Scaling social apps If you have lots of money, build everything yourself… Otherwise…
  • Gratuitous screenshot of app stats
  • Randomized trials for testing application features Running two profile designs simultaneously; users grouped by their network ids
  • Diagnosing / monitoring complex systems
    • App activity measure
  • Diagnosing / monitoring complex systems
    • Overlay deployments
  • When good sites go bad
    • Important to understand your app’s dependencies (yellow line is API call failures)
  • When good sites go bad
    • Effect on application functionality
  • fin
    • Questions / comments?
    • Contact: Raymond Chan ( [email_address] )