One huge mistake API companies make is forcing developers to understand every design decision they made inside.\n
Everyone says you don’t need good documentation. That’s only true if what you’re doing is stupid simple or completely sucks.\n
The most likely thing you’ll leave out is all the important shit. And that’s all the stuff you assume everyone knows.\n
Write every sample widget or application you can think of. Make them open source.\n
There’s never enough ways to give examples. Put them on your site, make gists, write articles.\n
Make sure you’ve got as many ways possible to communicate with your developers - email, web, groups, irc - all of them work.\n
There’s nothing better than making people “Ooh and Ahh” at the awesome stuff your API can do. Figure out how to show that off in 5 minutes. Double rainbows for audience participation.\n
There’s a ton of competition for developers these days - you won’t make friends sitting at home on the weekends. Sponsor as many as you possibly can - money or time are both great.\n
Everyone loves a little experimentation - sometimes you have to pay for it. When there’s 200 APIs to choose from, you’ve got to stand out (and your API may not be enough, gasp).\n
Tell everyone about them. Write blog posts, do videos, invite them to speak on your behalf.\n