This post is a reference to one of the articles I curated for the API Magazine. Below is a short intro.
…Developer ecosystems are multi-sided and involve numerous participants, which can make them incredibly complex. However, a clear understanding of how these ecosystems work can make it far easier to create one for your own core products….
Manfred Bortenschlager’s comment:
This is a very interesting take on the types and value of developer ecosystems. In summary the author sees 3 types:
1. Commodity
2. Add-on
3. Sell-with
Also P + S < M is discussed (see quote below). I would definitely add a V to the left side. What is the “value” of the developer in participating in an ecosystem? What problem is it solving for the developer?
“There is a very simple mathematical expression that can define whether you will succeed at garnering developer attention: P + S < M. That is, if it’s easier for a developer to build a product (that is, Participate) and it’s easier to start Selling and be promoted with your core service (the left side), and together, that effort is less than the capture of the total addressable Market that a developer can reasonably expect (on the right side), you will be successful.”
