Tom CardenJan 8, 2023

Thoughtful tech friends, if you were building a developer-facing API from scratch today what tech and SaaS would you use to get to market quickly with a quality product?

And: what features and considerations are “table stakes” for you to consider using someone else’s API?

#tech #apis #saas

Show threadMo Morgan

@randometc This in no way contributes to your question but it reminded me that I only very recently learned that 'table stakes' means the opposite of what I thought.

In vague answer to the question, in the spirit of MVP, I'd err on the side of high-as-possible availability, , detailed-as-possble documentation, few-as-possible (and release-numbered) features.

I appreciate these are probably the least helpful things you'll get back!

Jan 8, 2023 at 3:29pmWeb
Show threadTom CardenJan 8, 2023
@mo no that’s helpful! I didn’t have availability as a v1 goal, but the first two responses have mentioned it. If you were evaluating an API how would you assess availability? Do you just look at SLAs or do you want transparency into error rates, status/uptime/etc?
Show threadMo MorganJan 8, 2023
@randometc Errors are more interesting than uptime for me, if I had to choose. It's easier to catch unresponsive endpoints, but harder to cater for outbreaks of weirdness. But I don't know how representative I am, really.