Design of nine states. A lifetime for lost ingredients By Vance Spellman | Start up
M.Eastern UI teams are designing the first components. Interfaces are structured with component thinking. This often leads to holes in the “unpleasant path” for consumers. Places where users may or may not knowingly deviate from your ideal flow. As we learn system craft instead of pages, we should try to shape these lost states and create them with a component cycle that can help everyone. As I told him right away:
What happens First Does your component do anything? This may be the first time the user has seen it. It may not be activated yet. Basically, the component exists but does not exist Start.
2 its loading
Frightened state. In the perfect world, no one will ever see it. Sorry, we find ourselves. There are so many types it’s hard to say. Facebook does a great job of this:
3. No one
Your component has started, but it is empty. No content. Now is a good time to get the user to work (“Do it!”), Or reward them (“Good job, everything is taken care of”).
You have some data. At an input, this may be after the first stroke. In a list, this can happen when you have an item (or a leftover).
That’s what they usually think of you. What is the ideal state for this component? Your data is loaded, you have input, and the user is aware of it.
6. much more
Wow there! The user has somehow removed it. Lots of results (maybe you page them), lots of characters (maybe ellipses?), And so on.
There is nothing wrong with the component. An error occurred.
Ready to move on! This item meets your needs.
The user’s correct input was received through the request. They don’t have to worry about it anymore.