Designing your Product as a Platform


Published on

Learn how to deconstruct what it means to be "Open," as well as how to engage developers, leverage users, and shape your data to make your platform ready for commercial use.

Presented April 14th, 2009, at BayCHI:

Published in: Education, Technology
1 Comment
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Designing your Product as a Platform

    1. Designing Your Product as a Platform <ul><li>Micah Laaker, Yahoo! </li></ul>
    2. Caveats <ul><li>Platform = software framework that powers 2 or more products </li></ul><ul><li>Lots of technology “recommendations” that are mostly used for example purposes; before adopting technology, investigate for latest updates to this space </li></ul><ul><li>Internal platform? External platform? Similar considerations. </li></ul>
    3. Why?
    4. Open
    5. questions when embarking on Platform Design <ul><li>How “open” to go? </li></ul><ul><li>How do I leverage Users? </li></ul><ul><li>How do I shape my Data? </li></ul><ul><li>How do I engage Developers? </li></ul>4 1 2 3 4
    6. How Open? Photo: 1
    7. Open Source <ul><li>Free to use </li></ul><ul><li>Community contributions </li></ul><ul><li>Decentralized </li></ul><ul><li>High reliability </li></ul>Open 1/13
    8. Open Infrastructure <ul><li>Pay-as-you-go, only-what-you-need cloud computing </li></ul><ul><li>Outsource hosting, ops, and processing </li></ul>Open 2/13
    9. Open Architecture <ul><li>Anyone can mod your product... on your product </li></ul><ul><li>Plug’n’Play </li></ul>Open 3/13
    10. Open Standards <ul><li>Community-driven </li></ul><ul><li>Goal is inter-operability </li></ul><ul><li>Software and Hardware </li></ul>Open 4/13
    11. Open Ontology <ul><li>Describe what can not be seen </li></ul><ul><li>Future-proof your data </li></ul><ul><li>Goal is the Semantic Web </li></ul>Open 5/13
    12. Open Access <ul><li>APIs </li></ul><ul><li>Multi-channel access </li></ul><ul><li>3rd-party Developers/Partners can build on your platform </li></ul>Open 6/13
    13. Open Canvas <ul><li>Product becomes a vehicle for 3rd-party content </li></ul><ul><li>Fast food sites: your content to-go </li></ul>Open 7/13
    14. Open Content <ul><li>User is the editor by programming self-relevant content </li></ul><ul><li>Content comes to you when its ready </li></ul>Open 8/13
    15. Open Mic <ul><li>The product is populated entirely by users </li></ul><ul><li>Users own their content </li></ul><ul><li>Products support making/discovery of content </li></ul>Open 9/13
    16. Open Forum <ul><li>Users contribute ancillary data </li></ul><ul><li>Ratings, reviews, ranking, and link submissions </li></ul><ul><li>Heavy social interaction </li></ul>Open 10/13
    17. Open Door <ul><li>User as product decision-maker </li></ul><ul><li>Reveal operational details </li></ul><ul><li>Communication is open to all </li></ul>Open 11/13
    18. Open Borders <ul><li>Settings/configs can be imported/exported </li></ul><ul><li>No (product) commitments </li></ul><ul><li>Users can come-and-go </li></ul>Open 12/13
    19. Open Identity <ul><li>User as owner of identity </li></ul><ul><li>1 ID for many sites </li></ul><ul><li>Power to the people </li></ul>Open 13/13
    20. In what way(s) are you “open?”
    21. <ul><li>How does our product support our users? </li></ul><ul><li>How does our product engage our users? </li></ul>Leverage Users 2
    22. User Identity <ul><li>Support of OpenID as a relying party </li></ul><ul><li>Aggregation of cross-web identity </li></ul><ul><li>Leverage existing Relationship graphs </li></ul>Support function
    23. <ul><li>Access to User data and configurations </li></ul><ul><li>Lifestreaming </li></ul><ul><li>Attention XML </li></ul>User Broadcasting Support function
    24. User Feedback <ul><li>Suggestions </li></ul><ul><li>Metrics </li></ul>Support function
    25. User Contributions <ul><li>User is the owner and creator of your product’s content </li></ul>Engagement model
    26. User Enhancements User adds value to existing content/system: Engagement model
    27. User Extensions <ul><li>User as part of the product </li></ul><ul><li>Repairs, adds, and extends data </li></ul>Engagement model
    28. Leverage Users
    29. Shape Data 3
    30. Define the object
    31. Describe the Object <ul><li>Use Microformats/RDFa </li></ul><ul><li>Assist machines in making sensible decisions about your data </li></ul><ul><li>Improve SEO </li></ul><ul><li>Make future integrations/product ideas feasible with small investment upfront </li></ul>
    32. Connect the Object <ul><li>Support relationships between data </li></ul><ul><ul><li>Social Graph </li></ul></ul><ul><ul><li>Interests </li></ul></ul><ul><ul><li>Kevin Bacon for Data </li></ul></ul><ul><li>Use FOAF + XFN </li></ul>
    33. Distribute Objects <ul><li>Expose XML/feeds of your items </li></ul><ul><li>Map your feeds thru YQL Open Tables </li></ul>
    34. Data Model <ul><li>Define Objects </li></ul><ul><li>Describe Objects </li></ul><ul><li>Connect Objects </li></ul><ul><li>Distribute Objects </li></ul>
    35. Engage Developers 4
    36. Privacy/Security <ul><li>User’s creds. should never be shared </li></ul><ul><li>Industry-standard auth. protocol (OAuth) </li></ul><ul><li>User must control relationships </li></ul>
    37. Canvases <ul><li>3rd-party content inside your product </li></ul><ul><li>Technology: Apps & Widgets </li></ul>
    38. Service Exposure <ul><li>Make product functionality available as a service when applicable </li></ul>
    39. UI Components <ul><li>Build (and make available) UI as components when utilized in 2 or more locations </li></ul>
    40. Policy <ul><li>Define SLAs and Commercial TOU </li></ul><ul><li>Establish rate limits and means of surpassing </li></ul><ul><li>Communicate status of platform </li></ul>
    41. Developer Engagement <ul><li>Privacy/Security </li></ul><ul><li>Canvas support </li></ul><ul><li>Service exposure </li></ul><ul><li>UI Components </li></ul><ul><li>Policy </li></ul>
    42. Platform Design Task List <ul><li>Determine “Open-ness” </li></ul><ul><li>Define User Leverage model </li></ul><ul><li>Define Data model </li></ul><ul><li>Define Developer Engagement model </li></ul>1 2 3 4
    43. Open Platform One-Sheet UX User Exp. Dev. Exp. Data Model Open Source Open Infrastructure Open Architecture Open Standards Open Ontology Open Access Open Canvas Open Content Open Mic Open Forum Open Door Open Borders Open Identity
    44. In Closing <ul><li>Learn more about the Yahoo! Open Strategy: </li></ul><ul><li>Contact: Micah Laaker / [email_address] </li></ul>