Screens and States

A screen sketch shows where information and controls appear. A state model describes the information the app needs to display the screen correctly.

Consider an orders screen with saved orders. A refresh starts and then fails. The orders remain visible. The screen has content, a failed request, and possibly old data at the same time.

Do not force all of these facts into one choice between “loading,” “content,” and “error.” Some states can exist together.

1. Start with the user action

Draw a simple orders list with a refresh action and a way to open order details