Developer Experience is UX, except your user reads documentation instead of clicking buttons, and their frustration shows up as a churned integration instead of a support ticket.
DX is a real, measurable product discipline, not a vibe. Here's the practical breakdown:
DX dimension | What "good" looks like | What "bad" looks like |
|---|---|---|
Time to first successful call | Under 10 minutes from signup to a working request | Requires reading five pages and joining a Slack channel |
Naming consistency | customer_id everywhere, always | customer_id here, cust_id there, customerId somewhere else |
Error messages | Tell you what went wrong and how to fix it | Error: invalid request |
Predictability | Similar endpoints behave the same way | Every endpoint has its own quirky rules |
Sandbox / test environment | Full-featured, free, obviously separate from production | Missing, or subtly different from prod in ways that surprise you at launch |
The single highest-leverage DX metric most teams never measure is time to first successful call (TTFC). It's the API equivalent of activation rate in consumer products, and it correlates directly with whether a developer evaluating three competing APIs picks yours or gives up and picks a competitor's. If you don't know your TTFC today, that's a bigger finding than any feature request on your backlog.
WORKED EXAMPLE
Two payments APIs, functionally near-identical. API A requires an approval process before you get sandbox credentials — three business days. API B gives you a working test key the moment you sign up, with a pre-filled example request you can run immediately. Developers overwhelmingly evaluate API B first, build a prototype over a weekend, and by the time API A's approval email arrives, the decision is already made. This is not a hypothetical; it is the most common reason technically comparable APIs lose developer mindshare.
YOUR MOVE THIS WEEK
Sign up for your own API as if you were an outside developer, with no internal shortcuts. Time yourself from signup to your first successful request. If you don't personally know that number, you don't know your product.