Dan Abramov

Hmmm UI specifically, or UX? The who, what, when, where, why, and how are def the first things to look at when building software imho.

I find the distinction between UI and UX confusing so I use them interchangeably.

i know you're attempting to troll but i actually kinda agree with you on this

Not trolling! More like "what are our values" kind of exercise.

I think in terms of a sprint both are done simultaneously until when it is ready and fe consumes it

This is kind of where I was going with my comment about UI vs UX. In my experience, you figure out the UX first. Document it. Get sign off, if necessary. Then build UI and APIs, usually simultaneously.

I think it comes down to what you're more confident in backend devs will tell you to build the API first frontend devs will tell you to build the UI first I'm an API first kinda guy myself ^_^

I think Dan means the lib apis here as in code abstraction and not headless backend apis.

UI is probably the fastest way to realize that nobody wants your app anyway so you can move on to your next great idea.