When discussing the number of screens in mobile application design, the flow in which everything works correctly is mostly considered. However, the connection is interrupted, the user does not allow it, the process is left unfinished or the searched content cannot be found. If these situations are not in scope, interface decisions are made piecemeal during development.
Separate first use from next use
It is necessary to explain to the person who comes for the first time how the product works. Making the person come through the same explanations every day slows down the work. Consider the empty account, sample data, first transaction, and returning user cases separately. Plan the time to ask for permission based on the needs of the feature.
Show connection and transaction statuses
It should be understood whether a request is submitted, in progress, completed or failed. Review scenarios with the developer, such as repeat button presses during checkout or registration. The design should not give a definite success message in a situation where the server does not know what it is doing.
Write platform and accessibility decisions
The same visual approach can be used for iOS and Android; However, navigation, system permissions, and device behavior should be examined together. Large font size layout, touch targets, and screen reader order should also be included in the delivery notes. A presentation the size of a phone alone is not enough.
Add a status list next to the screen list at the beginning of the project. When the design budget and schedule are discussed in terms of these two lists, it becomes clearer what will be delivered. In the developer submission, explaining the return and error behavior is as important as the display of the screen.
Frequently asked questions
What does empty status mean in the mobile app screen list?
This is the situation the user sees when there is no data yet. Instead of just showing empty space, explain why there is no content and how to create initial content if necessary.
Why are the first use screen and subsequent use designed separately?
The new user may need clarification or permission information; Experienced users may want to return to their task quickly. Forcing two situations to flow the same can create unnecessary repetition.
