X-Road and API Economy - Ying & Yang or Fengshui?

X-Road and API Economy - Ying & Yang or Fengshui?

Presented at X-Road Community Event in Tallinn 2018 Sept 12th. Feel free to contact me if your event needs API and platform economy related inspirational presenter. Contact information in the slides.

Ca885e6fec0c28dd2effcd58e506778b?s=128

Jarkko Moilanen, PhD

September 12, 2018
Tweet

Transcript

  1. X-Road and API Economy Jarkko Moilanen (PhD), Author of API

    Economy book, Ministry of Education and Culture Jarkko.moilanen@minedu.fi +358 40 535 9066 Ying & Yang or fengshui? 90% API Economy point of view
  2. Jarkko Moilanen, Ministry of Education and Culture, Finland API Economy

    definition Company utilizes resources efficiently and quickly to create added value for own customers. Considering application developers as primary customers Building blocks utilized are own APIs and public APIs provided by other organizations (free or commercial) Source: Moilanen Jarkko et al, 2018, API-talous 101, Alma Talent
  3. Jarkko Moilanen, Ministry of Education and Culture, Finland What are

    different API types?
  4. Jarkko Moilanen, Ministry of Education and Culture, Finland API Economy

    customers Primary customer is application developer • Fit for purpose • Daily enjoyment to work with • Often API is given • Works with multiple APIs simultaneously • No polished sales pitch in developer portal! Secondary is management above the developer • Business level decisions • API cost structure • Can manage with nice polished material
  5. DX – focus on app developer needs API must have

    • Efficient (response time + purpose) • Reliable (performance + product future) • Easy onboarding (self service expected) • Getting started (console, examples) • Uptodate documentation • Support Jarkko Moilanen, Ministry of Education and Culture, Finland Value chain • Used in context • API fills a hole • API solves a problem in app development • Works with multiple APIs Developer eXperience & relations
  6. Jarkko Moilanen, Ministry of Education and Culture, Finland API catalogs

    are becoming new platforms Catalog provides discovery API catalogs contain more and more features found often in API management: • Developer relations • API key management • Monetization • Documentation management • …
  7. Over 700 governmental APIs Bias to US England (32 APIs),

    known world wise for work in digitalization Public APIs in public sector Jarkko Moilanen, Ministry of Education and Culture, Finland Jan 2018, programmableweb.com
  8. REST is de facto, GraphQL is niché API Economy trends

    Jarkko Moilanen, Ministry of Education and Culture, Finland ”Query APIs” are de facto, but events based APIs are rising fast (dedicated/hook based) 2010 App developer wants ”pull” datasets and/or API 2020 App developer expects ”push” streams and functions
  9. Jarkko Moilanen, Ministry of Education and Culture, Finland Questions to

    consider How do we utilize global catalogs as tools for discovery? Add APIs to ProgrammableWeb? How to match application developer expectations (DX) and relations (DevRel)? What kind of developer segment are we aiming at? public– private sector; private, partner API, Open data?