The document summarizes key discussions from the 2010 Web 2.0 Expo in San Francisco. Several topics were covered:
- Social media and APIs were major focuses, with discussions around introducing oneself on social platforms, the importance of APIs, and ensuring APIs are successful by making associated apps successful.
- Design elements for successful social games were outlined, including core gameplay, reducing complexity, appealing graphics, sound, and incorporating social actions and short play sessions with goals.
- Frameworks were presented for API development, including using REST over SOAP, keeping responses simple, and how sample code is important, as well as factors for success with social games like tutorials, increasing retention and growth through social features.
2. The buzz at web 2.0 expo Social @my-name, that’s the way to introduce oneself HTML 5 Mobile/ Location Everyone except Facebook talked about Facebook Twitter & Facebook Social interfaces, social media, social Ads… for everyone If you don’t have an API in 2010, you got to be kidding! API Integration Internet Open distribution, multi-platform, trans-media story-telling Innovation with iphone apps rules despite the walled garden Is the way to go, but with backward compatibility for now As an operating system – Tim O’reilly
5. Director, Market Development at BEA SystemsAPI : Evolve your business model The web is going from direct to indirect And beyond the browser Myth : Companies “supply” content that developers “demand” Reality: Companies “demand” attention of app-developers who “supply” innovation and distribution An API is successful if the App carrying it is successful. And an app is as strong as its weakest API Successful Apps will use many different API And they will carry those API everywhere
6. Framework for API development REST first SOAP developers : 200,000 REST developers : 2-5million Don’t invent something weird XML or JSON Keep responses simple and small Keep calls granular Use OAuth Sample code wins every time You’ll get it wrong the first time, so listen well
7. AmittMahajan Director of Engineering at Zynga Lead Developer (FarmVille) Co-Founder at MyMiniLife, Inc. Programmer at Epic Games Social Gold : the design of Farmville and other social games Design Elements Core game-play Natural game flow Increase decision points Reduce UI complexity Art Direction Appeal to fantasy, colorful Avoid excessive detail Humor adds character Sound Adds atmosphere Should be non-intrusive Capture the movie Social Actions Light (e.g. poke, like) Heavy (E.g. comment) Mixture of both Play sessions Keep them short Provide a goal for each player Link sessions together Moments of Joy “Cool events” in your game Make the player feel good Leverage art to create these
8. Framework to succeed with social games Capturing a player Hidden but effective tutorial Gradually introduce complexity Tackle non-design challenges too Increasing Retention Leave users wanting for more Give them a reason to come back Let their friends help Growing through social Make it valuable to be social Social actions in core, not forced Surface social actions by friends Sustaining players Regularly scheduled updates Long term value Events Enable Expression Social ROI Status symbols Enable investment Engage users first Make it easy to invest Surface the value they receive
9. The state of the internet Operating System- Tim Oreilly Ask yourself for a moment, what is the operating system of a Google or Bing search? What is the operating system of a mobile phone call? What is the operating system of maps and directions on your phone? What is the operating system of a tweet? The resources that are critical to this operation are mostly somewhere else Win32 API : an analogy Facebook platform : a case-study Version 1 was in-bound Version 2 is useful to others, outside “simply use our facilities, and the complexity will go away”
