Many enterprise IT departments have become big fans of an “API-first“ strategy. I think that in general, this is a bad idea. (Thread)
37
251
46
592
I like to think that API first design is more like - how do you imagine UX in consuming the API (cli, UI calls) and to start from there. In most ways when building from scratch it has proven a much better way than to start with domain design and to build APIs on top of it.
1
9
Replying to @npenkov
Domain design is a good start to figure out what systems (or applications, if you prefer) to build in the first place. After that, I prefer a use case/UI-driven approach

Apr 15, 2020 · 11:11 AM UTC

3
4
28
Replying to @stilkov @npenkov
UI-driven is still too distant. Human Centered Design is the place it needs to start. Who are the users, what are their problems, go from there. Few developers, even front end developers are equipped to even begin that conversation.
Replying to @stilkov
For most cases it goes both ways - UX to drive API and Domain driven bottom down from architecture - I would not exclude both ways, rather than work on how they join together.
1
Replying to @stilkov @npenkov
UX driven design fails to capture business logic complexities. It reduces the app to a set of isolated forms and wireframes that gives the customer a false feeling of simplicity. For business, business-driven design :D