Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Visualizing the Geography of Platform Boundary Resources

553 views

Published on

Presentation at HICSS 2017

Published in: Data & Analytics
  • Be the first to comment

Visualizing the Geography of Platform Boundary Resources

  1. 1. Visualizing the Geography of Platform Boundary Resources: The Case of the Global API Ecosystem Jukka Huhtamäki Rahul C. Basole Kaisa Still Martha G. Russell Marko Seppänen http://bit.ly/apiglobal2017preso http://bit.ly/apiglobal2017paper
  2. 2. Introduction
  3. 3. Why APIs? • APIs are replacing “traditional” interfirm relationships • APIs are lightweight boundary resources that allow for complementors to create value for the focal companies • APIs are artifacts of both lightweight software development and business strategy6.1.2017 4
  4. 4. API vs. platform economy 6.1.2017 6
  5. 5. 6.1.2017 7Biswarup Ganguly, CC BY 3.0
  6. 6. 6.1.2017 8
  7. 7. 6.1.2017 9
  8. 8. 6.1.2017 10 (Evans and Basole, 2016; Basole, 2016)
  9. 9. 6.1.2017 11 (Evans and Basole, 2016; Basole, 2016)
  10. 10. Why Geography? • Digitization is eliminating “distance” and therefore one can assume that geography would have a smaller role • At the same time, we see that large companies continue to be co-located 6.1.2017 12
  11. 11. We asked • Where are APIs located geographically*? • Is the geographical location of a company less important in the digital age? 6.1.2017 13
  12. 12. Method • Data collection using crawling and scraping • Data-driven visual network analytics • Semi-automated data curation process 6.1.2017 14
  13. 13. Data curation • 13,366 APIs and 6,271 mashups from ProgrammableWeb • Using URIs as identifiers, company location lookup using Crunchbase • Mapping the 6,218 APIs with location data to city-level entrepreneurial regions and global regions 6.1.2017 16
  14. 14. Results–two levels of analysis 1. Where are the APIs available globally? 2. How are APIs co-used between regions?
  15. 15. H 6.1.2017 18
  16. 16. API Co-use • Cf. co-citation analysis Three resulting connections (here regions): Twitter - Twitter Search Twitter - Google App Engine Twitter Search - Google App Engine
  17. 17. 6.1.2017 20 Regions connected on basis of API co-use
  18. 18. 6.1.2017 21 Regions connected on basis of API co-use
  19. 19. Conclusions
  20. 20. Takeaways • API ecosystem is highly concentrated to a few regions • API ecosystem is particularly flexible for actors to offer and consume services • API co-use is not API usage • Public APIs vs. Private APIs
  21. 21. Future work • Investigating the internal company-level network structure of entrepreneurial regions • Introducing dynamics to the analysis: API diffusion studies • How policy makers can facilitate the emergence of national and e.g. European API ecosystem? • How will the changes in international data governance policy impact the API ecosystem? 6.1.2017 24

×