Being the Gentle Giant

Helping people integrate for the long haul

@matt_mcclure

Zencoder Zencoder Zencoder

What makes an API good?

  1. Usefulness
  2. Design
  3. Support

Getting people to use an API

  1. Usefulness, design, support
  2. Good enough (parity with DIY)

Deciding on an API is a big deal

APIs can help developers focus on their product's core competency ...but takes control out of their hands

Taking the job seriously

Frequently, developers use an API because they're unable to perform the task

Helping developers integrate

Recognize that developers are going to vary wildly in skill

Easy Wins are fun

  • Everyone likes an easy win
  • Get to see basic usage examples
  • Get a quick feel for the service
  • Service gets to show off cool features

Easy ends quick

  • Quick hacks never get refactored
  • Never get a chance to show best practices
  • Doesn't exclude non-fits
  • "As for what the language is in, its php with java of course" - User

Talk about best practices

  • Guides
  • Blog posts
  • Documentation
  • Support
  • Dinner with their family

Provide integration libraries

Integration libraries should just get out of the way

Provide Feedback

Have developers' backs...be proactive.

Post-integration world

Once a customer is up and running, real support begins

How we like to think support will be

But really...

Be up front about downtime or potentially breaking changes

  • Let users know as soon as you confirm unscheduled downtime will occur
  • Eventually you'll have to deploy a chance that will break things...
    • Find all potentially affected users
    • Test recent requests
    • Contact them, contact them, contact them

Ask for feedback

  • Allows you to find annoyances, not just bugs
  • Lets developers know you care

Take pride

The world of open APIs is amazing.

Questions?

@matt_mcclure