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