Mobile App Design
Design mobile journeys for small screens, touch, and interruptions. You receive bilingual layouts and interaction specifications.
Why?
Mobile tasks happen with limited attention, variable connectivity, and different device settings. We make important actions reachable, define interrupted and error states, and document platform differences for implementation.
-
Reachable mobile actions
We consider touch targets, keyboard overlap, and navigation placement in the most important app tasks.
-
Defined interrupted states
Loading, connection loss, and permission scenarios are designed explicitly rather than left to implementation guesswork.
Our process
Define mobile tasks
We agree on platforms, priority tasks, device constraints, permissions, and connectivity scenarios.
Plan navigation and entry points
We map navigation, back behaviour, onboarding, and return paths for the agreed mobile journeys.
Design screen structures
We lay out key screens with touch targets, keyboard behaviour, content hierarchy, and safe areas in mind.
Develop visual states
We apply the visual system to loading, empty, error, and permission states, including agreed language and theme variants.
-
Review device interactions
We review prototypes at representative device sizes and document gestures, motion, text scaling, and reduced-motion alternatives.
Hand over platform specifications
We provide organised screens, assets, and platform notes, including agreed store assets and implementation review criteria.
Questions?
We can cover either or both within the agreed scope. Shared patterns are reused where appropriate, with platform-specific navigation and behaviour documented separately.
The agreed prototype connects priority tasks and states for review. It demonstrates interactions but is not a coded app or proof of production performance.
We agree on representative device sizes, define flexible layout behaviour, and review key screens with longer Arabic and English text and relevant text-size settings.
We include it when agreed in scope, with theme colours and component states documented. Adding it later requires reviewing contrast, assets, and all affected screens.
