Managing External Innovation: The Case of Platform Extensions

More documents

Recommendations

Info

The distinction between external and internal extensions originates with the microkernel architecture implemented by systems that need to be made available in multiple configurations that share common core functionality (Buschmann et al., 1996). Microkernel architecture has a minimal runtime (corresponding to the platform core) that provides hooks for adding extensions. All required functionalities are provided in the form of internal extensions that are integrated with the platform, while applicationspecific functionality may be added through external extensions. Internal extensions can remain extensions or can be incorporated into the platform core (Messerschmitt & Szyperski, 2003; Baldwin & Clark, 2006; Gawer & Henderson, 2007; Bosch, 2009). Extension status can change from external to internal or from internal extension to fully integrated with the core, as a platform evolves. This transition is not random, but usually follows a process controlled by the platform owners for managing extension development. One example is the Tabbed Browsing feature of the Firefox web browser, which was initially available as an external extension, but was later bundled as part of the Firefox core platform (Noll, 2007). 2.2.4 Regulatory instruments A platform ecosystem consists of the platform provided by the keystone, and a community of complementors. This community includes developers that build applications that sit on top of the platform, modules within its core, or components that extend platform functionality (Bosch & Bosch-Sijtsema, 2009). Boudreau and Hagiu’s (2009) study presented evidence of the important role that platform owners play as a 19
egulatory body within their network or ecosystem. Platform owners play the role of public authority, and they impose regulations to reduce the negative impact on the quality of the platform. There are number of instruments that are called “regulatory instruments” to help platform owners enforce regulations in their ecosystem (Boudreau & Hagiu, 2009). Regulatory instruments are a menu of options that platform owners use regulate relations among members in their network, such as pricing, platform design and legal means (e.g. licensing, developers’ agreement, etc) (Bosch & Bosch-Sijtsema, 2009; Boudreau & Hagiu, 2009). The regulatory menu of instruments includes: pricing, legal and contractual instruments, platform architecture, toolkits and sandboxes (Boudreau & Hagiu, 2009; von Hippel; Bosch & Bosch-Sijtsema, 2009). In our research we focused on instruments that platform owners are offering for extension development and quality assurance, such as toolkits (Thomke & von Hippel, 2002; Messerschmitt and Szyperski, 2003; Boudreau & Hagiu, 2009). In the next five sections we are going to discuss the different types of instruments in general, such instruments include: pricing, legal and contractual instruments, platform architecture, user toolkits, and sandboxes. Pricing and membership Pricing and membership are two forms used to regulate information access and transactions on the platform. Pricing or membership refers to the pricing schema set by the platform owner to charge third-party developers for gaining access rights to the 20
Page 1: MANAGING EXTERNAL INNOVATION: THE C
Page 4 and 5: ABSTRACT In recent years, high-tech
Page 6 and 7: TABLE OF CONTENTS 1 INTRODUCTION...
Page 8 and 9: 4.9 StarOffice.....................
Page 10 and 11: Figure 22. IBM HTTP Server communit
Page 12 and 13: Table 20. Collaboration modes for M
Page 14 and 15: 1 INTRODUCTION Iyer (2006) describe
Page 16 and 17: 2. How do platform owners encourage
Page 18 and 19: 1.4 Contributions This research con
Page 20 and 21: 2.1 Open innovation strategies and
Page 22 and 23: architecture, production process an
Page 24 and 25: Innovation Mall Elite Circle Innova
Page 26 and 27: platform and extends its functional
Page 28 and 29: Therefore, the platform architectur
Page 30 and 31: In a modular architecture, the modu
Page 34 and 35: platform, information, and service
Page 36 and 37: complexity of the platforms, and to
Page 38 and 39: • Contribution of external partie
Page 40 and 41: 3 RESEARCH METHOD This chapter desc
Page 42 and 43: 3.3 Method The research around regu
Page 44 and 45: 1. What are the models used by soft
Page 46 and 47: literature: i) regulatory tools, ii
Page 48 and 49: four projects was chosen using theo
Page 50 and 51: No. Section Description Data source
Page 52 and 53: Information was drawn from the plat
Page 54 and 55: 3.3.7 Identify strategies adopted b
Page 56 and 57: 4 WRITE UPS FOR PLATFORMS IN THE SA
Page 58 and 59: plug-in plugs and declares its depe
Page 60 and 61: Table 9. Collaboration modes for Ec
Page 62 and 63: selection of these new opportunitie
Page 64 and 65: products are based on Java technolo
Page 66 and 67: Table 10. Collaboration modes for I
Page 68 and 69: of that is adapting Firefox for use
Page 70 and 71: While not very prominent, there are
Page 72 and 73: as Extension Developer). There are
Page 74 and 75: Extension module Core module Spring
Page 76 and 77: Community structure Figure 15 shows
Page 78 and 79: The first stage is the extension pr
Page 80 and 81: The SpringSource.com offers a partn
Page 82 and 83:
modules: set of core modules 4 that
Page 84 and 85:
Table 14. Collaboration mode for th
Page 86 and 87:
Regulatory instruments The Apache H
Page 88 and 89:
modules themselves and the Apache R
Page 90 and 91:
Table 15 represents the collaborati
Page 92 and 93:
Platform architecture The OpenOffic
Page 94 and 95:
Community Council Charter 7 . The c
Page 96 and 97:
Table 16. Collaboration modes for O
Page 98 and 99:
OpenOffice.org also has established
Page 100 and 101:
External Uno Internal Uno OenOffice
Page 102 and 103:
Sun Microsystems developers Extensi
Page 104 and 105:
to each other over the spinal cord
Page 106 and 107:
eceives commit access to the source
Page 108 and 109:
None of the previous cases had that
Page 110 and 111:
development process, the commercial
Page 112 and 113:
Platform architecture MySQL server
Page 114 and 115:
process is restricted to MySQL core
Page 116 and 117:
sandbox, extension development proc
Page 118 and 119:
Table 22. Summary of platform cases
Page 120 and 121:
No 1 2 3 4 5 Platform Spring framew
Page 122 and 123:
Community structure In Table 23, th
Page 124 and 125:
External extension Platform core In
Page 126 and 127:
5.1.3 Model C Table 27 represents t
Page 128 and 129:
Table 28. Collaboration modes for m
Page 130 and 131:
Table 29. Summary of the platforms
Page 132 and 133:
Collaboration Model Model C Advanta
Page 134 and 135:
Table 32.Summary of platform cases
Page 136 and 137:
6 DISCUSSION 6.1 Strategies for man
Page 138 and 139:
4. Regulatory instruments are used
Page 140 and 141:
Platform architecture Governance st
Page 142 and 143:
6.2 Regulatory instruments for mana
Page 144 and 145:
Pricing P10 Toolkits Governance San
Page 146 and 147:
Another key finding was the case of
Page 148 and 149:
Third, conduct a longitudinal study
Page 150 and 151:
Chen, W. J., Kirstein, H., Krook, D
Page 152 and 153:
Hemrajani, A. (2006a). Chapter 6: O
Page 154 and 155:
Herzog, P. (2008). Innovation and t
Page 156 and 157:
Rossi, A., & Zamarian, M. (2006). D
Page 158:
von Hippel, E. (2001). PERSPECTIVE:
show all

Managing External Innovation: The Case of Platform Extensions

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?