UI Before API
Jean Bauer
Software Developer
twitter/jeanbauerr
at WAES
non-developers
Disclaimer for
How to create a successful product or feature?
How to create a successful product or feature?
Not that easy
Ok, but how does it relate to my code?"
It's common to develop code to
just work
Let's see
that in action
User
access our website
ourwebsite.com/jeanbauerr/projects
Check Jean's projects
ourwebsite.com/jeanbauerr/projects
Check Jean's projects
Request
to API
...
...
...
(prob. 3 seconds on slow 3g)
ourwebsite.com/jeanbauerr/projects
Check Jean's projects
Project #1
Team
Project #2
Team
Project #3
Team
Project #4
Team
After 2 ~ 3 seconds
users can see the most important content
Yay.
We did it.
ourwebsite.com/jeanbauerr/projects
Check Jean's projects
Project #1
Team
Project #2
Team
Project #3
Team
Project #4
Team
* New feature *
Request
to API
(prob. 3 seconds on slow 3g)
It could easily take +5s to load this page
Tech Solutions?
-
GraphQL
-
Custom Endpoints
-
SSR
How I think UI before API would prevent that?
Non-Tech Solutions?
Plan your deliverables
UX work
Feature lifecycle
UI work
API work
Launch & Feedback
Communication
More thoughts
- Lean UX
