Jump to content

Platform evangelism

Add links
From Wikipedia, the free encyclopedia
(Redirected from Developer advocate)

Platform evangelism (also called developer relations,[1] developer and platform evangelism,[2] developer advocacy,[3] or API evangelism[4]) is the application of technology evangelism to a multi-sided platform. It seeks to accelerate the growth of a platform's commercial ecosystem of complementary goods, created by independent (third-party) developers, as a means to the end of maximizing the platform's market share. This initiative focuses on providing developers the resources to innovate, participate, and provide feedback to grow the platform.[5]

Multi-sided platforms

[edit]
Main article: Two-sided market

A multi-sided platform creates value by bringing together two or more different groups who can create more value together than apart.[6] Examples include buyers and sellers at an auction; readers and advertisers of a newspaper; and people at an online dating service. The platform vendor can profit by capturing a portion of the money that changes hands.[7] Platform vendors can serve as de facto regulators of their markets.[8]

An example of platform evangelism is the Developer and Platform Evangelism Division at Microsoft, which coordinates the personal computer (PC) and server's programming model.[9] It also provides tools for the Microsoft.NET platform, facilitating synergies between this system's Enterprise Server products and the Windows platform.[9] According to Jim Allchin, the former Platforms Group Vice President, the division also provides support to millions of software developers focused on high-performance and affordable technologies.[10]

Developers and consumers

[edit]

Many platforms have only two sides: one of consumers and the other of independent (third-party) developers. Independent developers produce and sell complementary goods, also called "platform applications," directly to the platform's consumers. These applications rely on the platform's services to function. Generally speaking, consumers prefer a platform with more and higher-value applications, while developers prefer a platform with more and higher-paying consumers.[11]

Recent examples of two-sided platforms that successfully attracted both consumers and developers include Apple iPhone,[12][13] Nintendo Wii,[14] Adobe Flash,[15] and Microsoft Windows.[16]

Other examples include household electricity (for appliances), the farm tractor's three-point hitch (for farming implements), camera lens mounts (for interchangeable lenses), the Picatinny rail (for gun-mounted accessories), and media players such as record players, CD players, and DVD players (for media content).

Functions

[edit]

Platform evangelism establishes and nurtures a platform ecosystem,[17] which requires five simultaneous activities: 1) sales, 2) enablement, 3) feedback, 4) intelligence, and 5) regulation.

Ecosystem sales

[edit]

Ecosystem sales is the attempt to convince third parties to develop complementary goods for the platform's commercial ecosystem. The characteristics of successful platform evangelists[18] and salespersons[19] are essentially identical, including deep product knowledge, empathy, humor, integrity, communication skills, positive attitude, infectious enthusiasm, a sincere desire to help others, etc. The primary difference is in "hunger for money" among salespersons.[19] This is unlikely to be satisfied by technology evangelism, which is more likely to be a cost center than a profit center, and hence incapable of paying sales-like commissions.

Developer enablement resources

[edit]

This aspect of platform evangelism can be seen as vendor-sponsored change agency in the diffusion of an innovation (the platform). As such, platform evangelism is responsible for creating the resources that enable developers to progress swiftly through the innovation adoption process ("developer enablement resources").

Each different phase of the platform adoption process requires different developer enablement resources. It is the responsibility of the platform evangelist to ensure that each developer enablement resource comes into existence in a timely manner.

Ecosystem feedback

[edit]

Because developers will often choose an inferior platform if its rate of improvement suggests that it will soon become the superior platform,[20] even the superior platform must improve rapidly. To facilitate this rapid improvement, platform evangelism organizes and champions the feedback of ecosystem developers within the platform vendor.

Ecosystem intelligence

[edit]

Ecosystem intelligence gathers information about the activities and intentions of other platform vendors from sources in and around the developer ecosystem.

Ecosystem regulation

[edit]

To avoid the market failure of multi-sided platforms,[21] platform evangelism will often engage in de facto regulation of the commercial ecosystem that surrounds its platform.[8] Such regulation combines legal, technological, informational, and other instruments (along with price setting) to minimize the costs of externalities, complexity, uncertainty, information asymmetry, and coordination problems.

Platform competition and platform evangelism

[edit]

Often, many competing two-sided platforms―each offering roughly the same benefits on the developer side―start diffusing through a market at approximately the same time.[22] Each platform's vendor competes[23] with the other vendors, via platform evangelism, to gain market share among the market's potential developers.[24]

Self-fulfilling prophecy

[edit]

If it is expensive to re-develop an application to target a second (or third) platform, then developers will tend to adopt, first, the platform which they believe has the highest lifetime profit opportunity. This tends to become a self-fulfilling prophecy, in which the platform which is initially perceived to have the highest lifetime profit opportunity tends to accumulate the most applications, which then makes it more attractive to consumers, which makes it more attractive to developers, etc., in a virtuous cycle, until a critical mass (also known as a tipping point) is reached, such that it out-competes the other platforms…and eventually does indeed come to offer the highest lifetime profit potential, as prophesied. This makes it very important for a platform vendor to convince developers from the outset, even before the platform becomes commercially available to consumers,[22] that its platform will have the highest lifetime profit potential. This contributes to the high-tech industry's hype cycle.

Network effects, path dependence, and de facto standards

[edit]

If the market has strong network effects, then those platforms which gain the fewest early adopters may cease to exist, making them unavailable to later potential adopters. This is path dependence.[25] If the number of reasonable platform choices in a market falls to 1, then that "only reasonable choice" becomes the market's de facto standard (also known as its Dominant Design) by definition.

Switching costs, lock-in, and profitability

[edit]

If the cost of switching away from a de facto standard to a new alternative exceeds the benefit gained by the earliest market participants who make that switch, then the market will tend to become locked into the de facto standard, with its market share approaching 100%.[25] Markets that are highly interconnected are more resistant to change than less interconnected markets.[26] Lock-in tends to make a de facto standard impervious to incremental competition, such that only a disruptive innovation can displace it.[27] Owning a locked-in de facto standard can be a license to print money for a very long time.[28]

Mature share

[edit]

Not all markets become locked into a de facto standard, and indeed, many factors act against such an outcome.[29] However, owning the first platform to establish a critical mass of complementary goods, with high switch-out costs, can create first-mover advantages that can go a long way towards ensuring that one gets a viable share of the mature market.[30]

Means to an end

[edit]

Therefore, with regard to a two-sided platform's developer side, it is platform evangelism's responsibility to:

  • Increase the quantity and quality of the platform's complementary goods;
  • Provide potential developers of complementary goods with a compelling opportunity for profit;
  • Increase awareness of this opportunity among potential developers of complementary goods;
  • Reduce the cost and risk associated with developing complementary goods;
  • Increase the percentage of the market's complementary goods that are developed first, best, or only for its platform;
  • Increase the network effects generated by its platform and its complementary goods;
  • Increase the platform's switching-out costs, while decreasing its switching-in costs;
  • Oppose the efforts of competing platform vendors to do likewise.

In short, it is platform evangelism's responsibility to design, develop, maintain, and extend the size and health of the platform's ecosystem, such that potential developers will choose to participate first, best, or only in that ecosystem.

Ultimately, these are all means to the end of gaining the highest possible share of the developer side of the targeted market. Whether this is, in turn, a means to the end of maximizing share on the market's consumer side, or vice versa, depends on the platform vendor's pricing strategy.

  • If the platform vendor profits primarily from the developer side (as Adobe does with Flash), then maximizing developer share is the ultimate end.
  • If the platform vendor profits primarily from the consumer side (as Microsoft does with Windows), then maximizing developer share is a means to the ultimate end of maximizing consumer share.

Theory and management

[edit]

The economics of multi-sided markets have only recently been subject to academic scrutiny,[31][32][33][34] so the theory underpinning platform evangelism's regulatory function is likely to be poorly understood by its practitioners—a situation that has contributed to many disastrous market failures.[21]

More generally, evangelizing the developer side of a multi-sided platform can be seen as using social influence to accelerate the diffusion of an innovation, within a dynamic system, in the presence of network effects, for economic gain (to the platform vendor or to society as a whole). Therefore, a solid understanding of the theory and practice of social influence, diffusion of innovations, system dynamics, innovation dynamics, network effects, innovation economics, and the economics of multi-sided platforms is essential to the design and management of efficient and effective platform evangelism campaigns.

Most of the theory and practice of platform evangelism, as influenced by these theoretical underpinnings, has yet to be comprehensively documented, and is therefore not available to novice evangelists or their managers. Because the development of expertise in any domain takes considerable time and practice,[35][36] vendors of new platforms cannot reasonably be expected to have in-house expertise in designing and managing effective platform evangelism campaigns.

See also

[edit]

References

[edit]
  1. ^ "LinkedIn: People with a job title that includes developer relations". Retrieved 12 October 2012.
  2. ^ "Microsoft Creates New Division to Step Up Focus on Software Developers". Microsoft. Retrieved 29 June 2010.
  3. ^ "LinkedIn: People with a job title that includes developer advocate". Retrieved 12 October 2012.
  4. ^ "API Evangelism is Equal Parts Internal, Partner and Public Outreach". Retrieved 12 October 2012.
  5. ^ Alstyne, Marshall W. Van; Parker, Geoffrey G.; Choudary, Sangeet Paul (2016-03-31). "6 Reasons Platforms Fail". Harvard Business Review. ISSN 0017-8012. Retrieved 2019-11-09.
  6. ^ Eisenmann, Thomas; Parker, Geoffrey; Van Alstyne, Marshall W. (October 2006). "Strategies for Two-Sided Markets". Harvard Business Review (October 2006).
  7. ^ Rochet, Jean; Tirole, Jean. "Platform Competition in Two-Sided Markets" (PDF). Journal of the European Economic Association (October 2006). Retrieved 21 June 2010. {{cite journal}}: External link in |journal= (help)
  8. ^ a b Boudreau, Kevin; Hagiu, Andrei (2010). "Platform Rules: Multi-Sided Platforms as Regulators" (PDF). Platforms, Markets and Innovation. Edward Elgar. ISBN 978-1-84844-070-8.
  9. ^ a b Foley, Mary Jo (October 3, 2012). "Microsoft veteran Guggenheimer takes over Developer Evangelism team". ZDNet. Retrieved 2019-11-09.
  10. ^ Maher, Jennifer Helene (2016). Software Evangelism and the Rhetoric of Morality: Coding Justice in a Digital Democracy. New York: Routledge. p. 3. ISBN 9780415704243.
  11. ^ Haigu, Andrei. "Optimal Platform Pricing in Two-Sided Markets" (PDF). the RAND Journal of Economics (2004). Retrieved 21 June 2010. {{cite journal}}: External link in |journal= (help)
  12. ^ Heisler, Yoni (November 7, 2009). "iPhone App Store Hits 100K, Leaves Others in the Dust". PC World. Retrieved 21 June 2010. {{cite journal}}: External link in |journal= (help)
  13. ^ "Apple announces App Store downloads top 3 billion". AppleInsider. January 5, 2010. Retrieved 21 June 2010. {{cite journal}}: External link in |journal= (help)
  14. ^ McIntyre, Douglas (January 6, 2010). "Nintendo Wii Sales Soar Again". DailyFinance. Retrieved 21 June 2010. {{cite journal}}: External link in |journal= (help)
  15. ^ "Flash Player Version Penetration". March 2010. Retrieved 21 June 2010.
  16. ^ Keizer, Gregg (January 3, 2010). "Windows market share slide resumes". Computerworld. Retrieved 21 June 2010.
  17. ^ Adomavicius, Gediminas (June 2007). "Technology Roles and Paths of Influence in an Ecosystem Model of Technology Evolution" (PDF). Information Technology and Management. 8 (2): 185–202. doi:10.1007/s10799-007-0012-z. S2CID 33156757.
  18. ^ Lucas-Conwell, Frederic. "Technology Evangelists: A Leadership Survey" (PDF). Retrieved 21 June 2010.
  19. ^ a b Ruth, Amanda; Wysocki, Allen. "Top Sellers: Characteristics of a Superior Salesperson (SN004)" (PDF). University of Florida IFAS Extension. Retrieved 21 June 2010.
  20. ^ Plamondon, James (November 1991). "Apologia Windowia". Frameworks Magazine. Archived from the original on 2011-07-14.
  21. ^ a b Chapman, Merrill (9 July 2003). In Search of Stupidity: Over 20 Years of High-Tech Marketing Disasters. Apress. ISBN 978-1-59059-104-8.
  22. ^ a b Armstrong, Mark (2005). "Competition in Two-Sided Markets" (PDF). The RAND Journal of Economics. Archived from the original (PDF) on 19 May 2011. Retrieved 20 June 2010. {{cite journal}}: External link in |journal= (help)
  23. ^ Shapiro, Carl; Varian, Hal (Winter 1999). "The Art of Standards Wars" (PDF). California Management Review. 41 (2): 25. doi:10.2307/41165984. JSTOR 41165984. S2CID 154820597.
  24. ^ Economides, Nicholas; Katsamakas, Evangelo (May 2005). "Two-sided competition of proprietary vs. open source technology platforms and the implications for the software industry (Working Paper #05-02)" (PDF). Archived from the original (PDF) on 19 May 2011. Retrieved 20 June 2010.
  25. ^ a b Arthur, Brian W. (1994). Increasing Returns and Path Dependence in the Economy. University of Michigan Press. ISBN 978-0-472-09496-7.
  26. ^ Chakravorti, Bhaskar (2003). The Slow Pace of Fast Change: Bringing Innovations to Market in a Connected World. Harvard Business School Press. ISBN 978-1-57851-780-0.
  27. ^ Christensen, Clayton (1997). The Innovator's Dilemma: When New Technologies Cause Great Companies to Fail. Harvard Business School Press. ISBN 978-0-87584-585-2.
  28. ^ Christensen, Clayton (2003). The Innovator's Solution. Harvard Business School Press. p. 151. ISBN 978-1-57851-852-4.
  29. ^ Weyl, E. Glen (October 2008). "Monopolies in Two-Sided Markets: Comparative Statics and Identification" (PDF). Retrieved 21 June 2010.
  30. ^ Shy, Oz (2001). The Economics of Network Industries. Cambridge University Press. ISBN 978-0-521-80095-2.
  31. ^ Parker, Geoffrey; Van Alstyne, Marshall (2010). "Innovation, Openness and Platform Control". ACM Conference on Electronic Commerce. ISBN 978-1-60558-822-3.
  32. ^ Gawer, Annabelle (February 2010). Platforms, Markets and Innovation. Edward Elgar. ISBN 978-1-84844-070-8.
  33. ^ Evans, David S.; Hagiu, Andrei; Schmalensee, Richard (April 2008). Invisible Engines: How Software Platforms Drive Innovation and Transform Industries. The MIT Press. ISBN 978-0-262-55068-0.
  34. ^ Gawer, Annabelle (April 2002). Platform Leadership: How Intel, Microsoft, and Cisco Drive Industry Innovation. Harvard Business Press. ISBN 978-1-57851-514-1.
  35. ^ Ericsson, K. Anders; Krampe, Ralf Th.; Tesch-Römer, Clemens (1993). "The Role of Deliberate Practice in the Acquisition of Expert Performance" (PDF). Psychological Review. 100 (3): 363–406. doi:10.1037/0033-295X.100.3.363. S2CID 11187529.
  36. ^ Ericsson, Anders K.; Prietula, Michael J.; Cokely, Edward T. (2007). "The Making of an Expert" (PDF). Harvard Business Review. 85 (July–August 2007): 114–21, 193. PMID 17642130. Archived from the original (PDF) on 2012-02-24. Retrieved 2010-06-21.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Platform_evangelism&oldid=1213803915"