This document summarizes a presentation on how to improve APIs by focusing on the developer experience. The presentation outlines four simple rules for better APIs: 1) Give developers reasons to build on the API, 2) Make developers successful faster, 3) Don't violate developers' trust, and 4) Listen to developers. It discusses common frustrations developers have such as a lack of purpose or documentation, difficulty getting started, and lack of support. The presentation urges API providers to put themselves in developers' shoes and treat them and their APIs as products to improve adoption.
3. Rapid API Workshop Webinar Series
Mapping
out
your
API
Strategy
PragmaAc
REST:
API
Design
Fu
10
PaJerns
of
Successful
API
Programs
API
Metrics
–
What
to
Measure?
API
Technology
&
OperaAons
Today:
Your
API
Sucks!
PCI
Compliance
and
APIs
4. THIS TALK
IN A NUTSHELL
•
User
experience
wins
•
API
users
=
developers
•
Developer
experiences
(generally)
suck
•
But
they
don’t
have
to…
16. Krug says:
1. People don’t read pages. They scan them.
2. People don’t make optimal choices. They
satisfice.
3. People don’t figure out how things work.
They muddle through.
65. Four simple rules
1. Give developers every reason to build
2. Make them successful faster
3. Don't violate their trust
4. Listen
66. Rapid API Workshop Webinar Series
Mapping
out
your
API
Strategy
PragmaAc
REST:
API
Design
Fu
10
PaJerns
in
Successful
API
Programs
Today:
API
Metrics
–
What
to
Measure?
API
Technology
&
OperaAons
Your
API
Sucks!
Next:
PCI
Compliance
and
APIs