Oct. 4, 2011 webcast top 5 tips for building viral social web applications and sites jonatjan le blanc
•Download as PPTX, PDF•
0 likes•1,574 views
Taken from lessons and technologies from "Programming Social Applications", this webcast will cover the top 5 tips that every web and application developer should know for using social techniques to increase traffic, build viral channels, and increase community involvement. We will look at mistakes that companies make when building social features into websites and applications, and how to prevent and solve those problems with open source technologies and techniques. This will take us on a tour of implementations from real products and showcase how emerging open source social technologies can be used to build rich social ecosystems. Presented by: Jonathan LeBlanc
Recommended
More Related Content
What's hot
What's hot (18)
Viewers also liked
Viewers also liked (20)
Similar to Oct. 4, 2011 webcast top 5 tips for building viral social web applications and sites jonatjan le blanc
Similar to Oct. 4, 2011 webcast top 5 tips for building viral social web applications and sites jonatjan le blanc (20)
More from O'Reilly Media
More from O'Reilly Media (20)
Recently uploaded
Recently uploaded (20)
Oct. 4, 2011 webcast top 5 tips for building viral social web applications and sites jonatjan le blanc
- 2. http://shop.oreilly.com/product/06 36920014201.do Foundation for socializing applications and websites. Open Source foundation.
- 5. Build for the relevant social & interest graphs
- 6. When do you integrate social outreach channels in your products?
- 9. • First round of “Mafia Wars” as an initial game partner for YAP in 2009. Failed to produce high install rates and difficult to integrate. • Second integration of “Mafia Wars” and “FishVille” in late 2010. Higher install rates, new viral channels and little integration pain.
- 11. finger jleblanc@yahoo-inc.com Login name: jleblanc In real life: Jonathan LeBlanc Home phone: 123-4567 Office: San Jose, CA Last Login: Tue Oct 4 12:41 on ttys000 jleblanc@x.com http://www.jcleblanc.com
- 15. curl http://gmail.com/.well-known/host-meta <XRD xmlns='http://docs.oasis-open.org/ns/xri/xrd-1.0' xmlns:hm='http://host-meta.net/xrd/1.0'> <hm:Host xmlns='http://host-meta.net/xrd/1.0'> gmail.com</hm:Host> <Link rel='lrdd' template= 'http://www.google.com/s2/webfinger/?q={uri}'> <Title>Resource Descriptor</Title> </Link> </XRD>
- 16. curl http://www.google.com/s2/webfinger/?q=nake dtechnologist@gmail.com The User Profile: http://www.google.com/profiles/nakedtechnologist The portable contacts link: http://www- opensocial.googleusercontent.com/api/people/118167121283215553793/ The public Google Buzz feed: https://www.googleapis.com/buzz/v1/activities/118167121283215553793/@public
- 17. Understand your sharing model and integrate early
- 19. The Opt-in Model The Opt-out Model
- 31. • Is the content coming from a trusted source? • How does the publisher prevent spam or abuse? • How does the publisher ensure the quality of the updates?
- 32. 1. Subscriber sends signed request to publisher (e.g. using acct:johndoe@subscriber.example.com). 1. Publisher performs discovery on endpoint to verify identity provider. • Webfinger • LRDD (Link-based Resource Descriptor) 2. Provider verifies signature via public keys obtained during discovery.
- 33. Use the work that other companies have invested in
- 35. • Third round partner integrating with our social services. • They created their own OAuth implementation since we did not have an appropriate SDK. • Integration failed near completion of the code.
- 36. http://ogp.me/
- 38. Geo <span class="geo"> <span class="latitude">52.48</span>, <span class="longitude">-1.89</span> </span> vCard <div class="vcard"> <div class="fn">Joe Doe</div> <div class="org">The Example Company</div> <div class="tel">604-555-1234</div> <a class="url" href="http://site.com/">http://site.com/</a> </div>
- 42. <html xmlns:og="http://ogp.me/ns#"> <head> <title>Restaurant at Wente Vineyards – Livermore</title> <meta property="og:url" content="http://www.yelp.com/biz/gATFcG9HTaXJpg"> <meta property="og:type" content="restaurant"> <meta property="og:title" content="The Restaurant at Wente Vineyards"> <meta property="og:image" content="http://media2.px.yelpcdn.com/iVSnIs"> ... </head> ... </html>
- 43. • Basic Metadata • Location • Contact Information • Video Data • Audio Data • Objects • Activities • People • Businesses • Places • Groups • Products and Entertainment • Organizations • Websites
- 44. Build for all available outlets
- 45. • Facebook was a primary outlet for Zynga when they integrated OpenSocial containers. • They built an abstraction layer on top of every platform. One game, multiple endpoints.
- 46. Foundation Specification for Social Applications and Containers. Shindig is a practical implementation of OpenSocial. Partuza is a sample social container.
- 49. Use emerging social technologies
- 51. Failure to move quickly on new technologies. Security prevented innovation. Not seen as a technology leader.
- 52. Do you or your companies allot time for emerging technologies?
- 53. Authorize applications and sites to do something on your behalf. Signing done on side of integrator. Lengthy integration process.
- 54. Significantly improved integration time. Communication over HTTPS
- 55. Jonathan LeBlanc Twitter: @jcleblanc E-Mail: jleblanc@x.com http://www.slideshare.net/jcleblanc
- 56. Special Offer for Webcast Attendees Programming Social Applications Visit http://oreilly.com/webcasts to view upcoming webcasts and online events.