Developer Ecosystems
•
4 likes•1,277 views
The document proposes a framework for building a successful developer ecosystem for multi-sided platforms. It suggests platforms must balance developer needs and platform strategy. The framework maps developer needs on the y-axis and platform strategy on the x-axis. Key design elements for developer needs include API model, rewards, development environment, and support. Platform strategy elements include platform model, control, governance, and addressing multi-homing and network effects. The document outlines these elements and surveys developers on needs.
![Agenda ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
Viewers also liked
Viewers also liked (10)
Similar to Developer Ecosystems
Similar to Developer Ecosystems (20)
More from Ramamurthy Prakash
Developer Ecosystems
- 1. Comprehensive Project – EPGP 2011 Developer Network Strategy for Multi-sided Platforms Shylender Ramamurthy Ramamurthy Prakash B
- 3. Developer Network Strategy Framework
- 4. Design Elements – Developer Needs
- 5. Design Elements – Platform Strategy
- 6. Platform Life cycle2 Shylender & Ramamurthy – EPGP 2011
- 8. Developer Ecosystem 4 Shylender & Ramamurthy – EPGP 2011
- 9. Developer Network Strategy Framework Platform dies Platform thrives Developer Needs No one adopts Developers move Platform Strategy 5 Shylender & Ramamurthy – EPGP 2011
- 10. Framework - Platform Mapping Developer needs High Low Android iPhone MySpace Bada Yahoo! Facebook Twitter Force Windows Mobile High Low Platform Strategy 6 Shylender & Ramamurthy – EPGP 2011
- 12. Rewards & Recognition
- 15. Evangelism
- 16. Communication
- 17. Connect with peers
- 18. Learning curve
- 19. Support
- 20. Platform Model
- 21. Platform Control
- 24. Multi-homing
- 25. Network effects
- 26. Scalability7 Shylender & Ramamurthy – EPGP 2011
- 27. Developer Needs - Survey 8 Shylender & Ramamurthy – EPGP 2011
- 29. Rewards & Recognition
- 30. Development environment (IDE)
- 31. Certification process
- 32. Application discovery
- 33. Evangelism
- 34. Communication
- 35. Connect with peers
- 36. Learning curve
- 37. Support9 Shylender & Ramamurthy – EPGP 2011
- 39. Network effects
- 40. Pricing
- 41. Chicken & Egg
- 42. Tipping
- 43. Envelopment
- 44. Multi HomingSide 1 Side 2 Platform Provider 10 Shylender & Ramamurthy – EPGP 2011
- 45. Platform models 11 Shylender & Ramamurthy – EPGP 2011
- 47. Platform Control
- 50. Multi-homing
- 51. Network effects
- 52. Scalability12 Shylender & Ramamurthy – EPGP 2011
- 53. Platform life cycle 13 Shylender & Ramamurthy – EPGP 2011
- 54. Thank you 14 Shylender & Ramamurthy – EPGP 2011
Editor's Notes
- API model exposed depends on the Platform model ( Integrator etc ) & control ( extend the platform or not ) as to whether more business functionality can be exposed or notApplication discovery ( market place ) might impact on how Platform governance is done and vice versaEasier Learning curve makes it more developers to adopt whereas at the same time Platform membership might inhibit developers joiningHigher R&R costs might require exclusivity which might move developers against multi homingEasier certification process can bring in more developers but that might also bring in negative direct network effects for Developers