Managing External Innovation: The Case of Platform Extensions

Managing External Innovation: The Case of Platform Extensions Managing External Innovation: The Case of Platform Extensions

www3.carleton.ca
from www3.carleton.ca More from this publisher
18.04.2014 Views

complexity of the platforms, and to hide low-level aspects of the platform from extension developers. Prügl & Schreier (2006) distinguish between low-end and high-end toolkits; depending on the scope describing the design possibilities users can explore using the toolkit. They found that in addition to the toolkits offered by the platform owner, which tend to be more basic, users have created more advanced toolkits to meet the needs of specific user groups. Providing toolkits is not restricted to platform owners, as users develop toolkits that serve the users’ needs in the process of developing elements for the platform. An example is the K Desktop Environment (KDE) that was developed by Matthias Ettrich (Spinellis & Gousios, 2009a). Software sandboxes The software sandboxes are another form of user toolkits that can be provided for innovation. Traditionally sandboxes defined as a controlled environment that provides at least a minimal functionality needed to accurately test the developed software (Venugopalan, 2005). Sandboxes provide an isolated environment for untested code changes and an experimentation space away from the original code-base repository. There is no uniform definition of what a sandbox comprises. A testing server, a mirrored production environment (working directory), and a development server are different formations of sandboxes that exist today. In the context of web application development, a sandbox is a staging or development server that is logically separated from the production server. There is even a more 23

specialized notion of sandbox in the sense of an environment for executing non-trusted applications (such as applets). A sandbox can also include the capability to test multiple platform configurations where the module being tested is combined with other modules and the opportunity to simulate environmental conditions to exert the module (for example, if deployment of the module requires the presence of special hardware, or should be tested with multiple users) (Bosch & Bosch-Sijtsema, 2009). 2.3 Lessons learned The lessons learned from the literature are: • The research regarding the development of platform extensions is still in its early stages, so there is not much literature on the strategies and frameworks used to manage the platform extension development process. • Open innovation leads to porous boundaries between firms and their surrounding environment, which facilitates information flow with external parties, but also results in a loss of direct control over the quality of product features. • Elements of the architecture of participation such as technical design, development process and intellectual property are important enablers for leveraging innovation and controlling quality in the platform network. • There are different models to open up the innovation process and collaboration governance but there are no frameworks to control the quality of the outcome. 24

specialized notion <strong>of</strong> sandbox in the sense <strong>of</strong> an environment for executing non-trusted<br />

applications (such as applets).<br />

A sandbox can also include the capability to test multiple platform configurations where<br />

the module being tested is combined with other modules and the opportunity to simulate<br />

environmental conditions to exert the module (for example, if deployment <strong>of</strong> the module<br />

requires the presence <strong>of</strong> special hardware, or should be tested with multiple users) (Bosch<br />

& Bosch-Sijtsema, 2009).<br />

2.3 Lessons learned<br />

<strong>The</strong> lessons learned from the literature are:<br />

• <strong>The</strong> research regarding the development <strong>of</strong> platform extensions is still in its early<br />

stages, so there is not much literature on the strategies and frameworks used to<br />

manage the platform extension development process.<br />

• Open innovation leads to porous boundaries between firms and their surrounding<br />

environment, which facilitates information flow with external parties, but also<br />

results in a loss <strong>of</strong> direct control over the quality <strong>of</strong> product features.<br />

• Elements <strong>of</strong> the architecture <strong>of</strong> participation such as technical design,<br />

development process and intellectual property are important enablers for<br />

leveraging innovation and controlling quality in the platform network.<br />

• <strong>The</strong>re are different models to open up the innovation process and collaboration<br />

governance but there are no frameworks to control the quality <strong>of</strong> the outcome.<br />

24

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!