Developer eXperience is the key - APInf Oy

Presented at API Business Lab at Valmet Automation - API driven economy mini industry hackathon.

Transcript

1. Developer eXperience is the key APInf Oy Apinf.com
2. Get control of your digital resources APInf Oy Started 3/2015 (1/2017) API -strategy consultancy API -catalog and management • apinf.io • REST & MQTT 21 employees • In Tampere, Brazil, Russia and India Jarkko Moilanen • APItalist and API -evangelist • Customers and Communities team lead
3. API providers (3rd party) App Developers (3rd party) App Developers (3rd party) App Developers API providers
4. APIs are implemented efficiently, easy to use, fast to on-board and reliable How?
5. Customer…. App/service Developer has problems and needs (3rd party) API to solve it Get under developer skin and stick with them Developer program Good, now we know that customer wants...
6. API Product Owner, strategic role, ”excel person”, API Economy expert
7. APIOps is about building standardized API value chain automation Experimentation community with hacker mentality and values Medium.com/apiops
8. Triangle... For whom app developers Why comes from APItalist How it’s done from APIOps
9. Focus on Developer eXperience ...why?
10. You have 3 minutes to cross the chasm and get (paying) customers to your API
11. TOP requirements Easy to use Top performance Reliable Agile
12. We have API documentation, that is our Developer eXperience
13. We have API documentation, that is our Developer eXperience Dude! No!
14. ”We have Swagger spec, isn’t that enough?”
15. ”We have Swagger spec, isn’t that enough?” NO! It’s a good start, make use of it.
16. Create great Developer eXperience • What problem it solves? (Why should I care) • How do I take it into use? (barrier) • Support? (uptodate documentation + code level examples + code generation) • What does it cost? (plans) • What the future? (continuum) • Show me the reliability (history, performance + who’s responsible)
17. Measuring • 3 - 30 – 3 rule – 3 seconds to understand why API exists – 30 seconds to find API endpoint – 3 minutes to have API in use • Time to First Hello World – Pick a developer and ask to do ”hello world” with your API
18. People are now fine People are now fine tuning boring out-dated tuning boring out-dated API doc solutions. API doc solutions. Noboby reads docs Noboby reads docs Bomb is on the way Bomb is on the way already already
19. Future API DX is based on Chatbots + Artificial intelligence
20. APInf API-bot Immediate API support & on-boarding Contextual support Scale you API support Integrate where you users are slack, flowdock, messenger... Hitch API Assistant 42
21. Future DX is adaptive
22. Take aways • Provide TOP Developer eXperience! • Get at least one APItalist in your team! • Use standars (such as Swagger) – easier to automate • Security! Don’t do what Nissan did… • Learn to use AI and bots! Contact for further mentoring @kyyberi Jarkko@apinf.io