Abstract
Prior research documents the significance of using platform boundary resources (e.g. application programming interfaces) for cultivating platform ecosystems through third-party development. However, there are few, if any, theoretical accounts of this relationship. To this end, this paper proposes a theoretical model that centres on two drivers behind boundary resources design and use resourcing and securing and how these drivers interact in third-party development. We apply the model to a detailed case study of Apple's iPhone platform. Our application of the model not only serves as an illustration of its plausibility but also generates insights about the conflicting goals of third-party development: the maintenance of platform control and the transfer of design capability to third-party developers. We generate four specialised constructs for understanding the actions taken by stakeholders in third-party development: self-resourcing, regulation-based securing, diversity resourcing and sovereignty securing. Our research extends and complements existing platform literature and contributes new knowledge about an alternative form of system development.
