Your API Deserves More Respect: Make It A Product

22
Make it a Product! Your API deserves more respect

description

Your API Deserves More Respect: Make It A Product Andrew Seward, Technical Product Manager, Esendex Your API is a product in its own right - it has its own customer base, its own target market, customer journeys, interface considerations, profit margins, features, bugs, strengths and weaknesses. That idea is an easy sell for most of us here, but how do you get your whole company on board, particularly when many of your colleagues haven't heard of APIs before? I will share my experience of changing how Esendex thinks about and approaches its API - where we were with our API and how we went about raising it to be our main product. What worked, what didn't, what problems we encountered, how we overcame them and what we're still trying to figure out. We also want to hear from you and your experiences so we can all benefit from the conclusions you've drawn.

Transcript of Your API Deserves More Respect: Make It A Product

Page 1: Your API Deserves More Respect: Make It A Product

Make it a Product!Your API deserves more respect

Page 2: Your API Deserves More Respect: Make It A Product

Today we will cover

● Brief introduction● Your API is a Product

○ Why that matters● Treating your API as a product● Getting everyone on board● Discussion

Page 3: Your API Deserves More Respect: Make It A Product
Page 4: Your API Deserves More Respect: Make It A Product

YOUR API IS A PRODUCT

Features

Quirks Customer journeys

Bugs

Things that are great

Things that suck

Customers

PackagingInstructions

People who love it

People who don’t love it

Page 5: Your API Deserves More Respect: Make It A Product

Does your API have

● A target audience?● A marketing strategy?● A sales strategy?● A development plan?● A support process?

Page 6: Your API Deserves More Respect: Make It A Product

Your users don’t want an API

They want a product that solves their problem

Page 7: Your API Deserves More Respect: Make It A Product

Why don’t we already treat all APIs as

Products?

Page 8: Your API Deserves More Respect: Make It A Product

A Mars bar

Page 9: Your API Deserves More Respect: Make It A Product

An API

?

Page 10: Your API Deserves More Respect: Make It A Product
Page 11: Your API Deserves More Respect: Make It A Product

How do we talk about our APIs?

Page 12: Your API Deserves More Respect: Make It A Product

Did you mention any of these things

● REST● How great it works with programming

language X● How it’s secured (API keys, OAuth, Basic

auth, etc.)

Page 13: Your API Deserves More Respect: Make It A Product

Talk about what you can do with it and why

Not how it works

Page 14: Your API Deserves More Respect: Make It A Product

Less of this

Page 16: Your API Deserves More Respect: Make It A Product

APIs as products

When talking about your API…

Talk about these first: ● What it does● How customers can benefit from it● How easy it is to use

Talk about these later:● How does what it does● How you integrate with it● How RESTful it is● How well it works with ELK stacks and Hadoop clusters,

and C#, Java, PHP, Node, Scala, Ruby, Python, Perl, Lisp, Ada, Swift...

Page 17: Your API Deserves More Respect: Make It A Product

Getting the team on board

Page 18: Your API Deserves More Respect: Make It A Product

API Training

Page 19: Your API Deserves More Respect: Make It A Product

Make sure everybody understands

● What your product is● Who uses it● How they benefit● How it performs● How we talk about it

Page 20: Your API Deserves More Respect: Make It A Product

Change how you talk about your API

to change how you think about it

Page 21: Your API Deserves More Respect: Make It A Product

Today we covered

● Brief introduction● Your API is a Product

○ Why that matters● Treating your API as a product● Getting everyone on board

Page 22: Your API Deserves More Respect: Make It A Product

Discuss