There are many answers but the essence of this presentation from #CraftConf 2015 is that puppies and APIs are long-term commitments that most of us aren't ready for until we can show that we have thought through all the implications.
Share what you learn This is Dave and I at PLOP 2005. We’re grateful to the people who shared what they’ve learned. That’s why I’m going to share some things I’ve learned today.
Public API with real users doing business-valuable things in a competitive environment It also means that when I say API (in this presentation) I mean...
Public API with real users doing business-valuable things in a competitive environment It also means that when I say API (in this presentation) I mean...
Public API with real users doing business-valuable things in a competitive environment It also means that when I say API (in this presentation) I mean...
Public API with real users doing business-valuable things in a competitive environment It also means that when I say API (in this presentation) I mean...
Public API with real users doing business-valuable things in a competitive environment It also means that when I say API (in this presentation) I mean...
1 2 3 4 Private API Consumer-facing UI Public API Ship it! Building a new feature First you build a private API then you build the consumer-facing product on top of it then you expose a public API that others can use and then you find out if it’s a good idea.
• You find yourself saying HATEOAS to angry people and it doesn’t make them less angry about the lack of documentation • You discover that the ways people want to use your APIs don’t map cleanly to the collections of resources that you designed Costs and consequences
• You discover that you need client libraries for a variety of languages • You discover painful trade-offs involving API keys and OAuth Costs and consequences
Google Translate and abuse Translate was sunset and then revived with a pricing plan because that’s the only way to control the kinds of abuse that happens with machine translation
Customers? You know who the potential customers and competitors are. You know how you will drive adoption of your API amongst those customers and in the face of competitive pressure
Competitors? You know who the potential customers and competitors are. You know how you will drive adoption of your API amongst those customers and in the face of competitive pressure
I’ve covered a lot of the pitfalls involved in launching a public API and hopefully it’s made you think twice. You now realise that the free puppy has hidden costs but my goal wasn’t to scare you away.