Mobile app design

Designing the states nobody shows in portfolios

App design portfolios show the happy path: a full feed, a completed profile, a successful payment. Real users spend a lot of time in other states. The empty list on first launch. The spinner while data loads. The error when the network drops. The form with a field filled in wrongly. When designers skip these, developers improvise them under deadline, and that is where an app starts to feel unfinished.

We design every screen in all its states as part of the scope, not as an extra. For each one, we ask what the user sees, what they can do next, and how they recover. An empty state that explains what to do first is often the most important screen in the onboarding.

• Empty: first use, no results, nothing saved yet
• Loading: what shows while waiting, and for how long
• Error: what went wrong, in plain words, and how to fix it
• Offline: what still works without a connection

Platform conventions save users effort

iOS and Android users have learned different habits: where the back button is, how navigation works, what a long press does, how settings look. An app that ignores those habits makes people think about the interface instead of the task.

We follow Apple's Human Interface Guidelines and Google's Material Design where they matter, and keep brand expression for colour, type, illustration and motion. Tap targets meet the recommended minimum sizes, and text and colour contrast meet accessibility guidelines, which also makes the app easier to use in bright sunlight.