How to avoid miscommunication between engineers and designers
Sometimes, I use React in order to develop front ends. However, before start creating them, I notice that specifications are not enough. The lacking specifications are about cases of emptiness, loading, and errors. For example, I would like you to imagine that an engineer is developing a page in which registered users are showed. The specification that associated with the page tells him what the view of the page is like when some users are registered. However, what if no users are registered? What if the page is being loaded for a long time?(In this case, execution process such as SQL is not good). What if some errors happen? We have to take such patterns into consideration. In order not to miss those patterns, I would like to recommend UI stack.
UI stack
It is a framework for thinking about the views of pages. We won’t miss states of pages such as loading, error, and blank state. Engineers and designers can communicate with each other more smoothly by using UI stack like “How about loading state?”.
