11. 11
@girlie_mac
11
Bad UX: User Reactions
When a person tries to [pour a cup of coffee at 7-Eleven]:
1. Confused
2. Trial & error
3. Frustrated
4. Repeat 2 - 3
5. Totally pissed off
12. 12
@girlie_mac
12
Bad DX: Developer Reactions
When a dev tries [API with poorly written docs / No code samples]:
1. Confused
2. Trial & error
3. Frustrated
4. Repeat 2 - 3
5. Totally pissed off
14. 14
@girlie_mac
14
Bad DX Examples: APIs
● Badly designed APIs
○ Bad naming conventions
○ Inconsistent names, methods, etc.
○ Non-verbose error messages
● Poor documentation
● Operational problems
○ Unstable - 5xx errors
15. 15
@girlie_mac
15
Bad DX Examples: Docs & Tuts
● No documentation
● Bad browsing experience, no ref links
● No diagrams, screenshots, pictures etc.
● Too complex
● Outdated materials
● Too much marketing content
● PDF everything (Docs != Whitepaper)
18. 18
@girlie_mac
18
L10N & I18N
“English is the universal language. Developers should
learn English”
- said, ex-Big Co. Dev Advocate
ARE YOU F’ING SERIOUS!?
20. 20
@girlie_mac
20
Know Your Developers
★ Get stats / Analytics
○ Where are they?
○ Which OS? etc.
★ Language? Programming lang & Spoken lang
★ Listen to devs in person & online
★ Conduct surveys
★ Read feedbacks (Tweets, Support)
★ Use the data & brainstorm ideas