Mobile app UX design
Principles, patterns and conventions for building applications people actually want to use
Designing a mobile app is not about adapting a website to a smaller screen. The usage context is radically different: users interact with one hand, on the move, with fragmented attention and in short sessions. Every design decision must respond to these conditions.
Mobile UX design spans information architecture and navigation patterns through to gestures, micro-interactions and accessibility. This guide covers the core principles and conventions that distinguish a well-designed app from one that breeds frustration.
Gesture and interaction design
Gestures are the interaction language of mobile apps. Swiping, pinching, long-pressing and dragging are actions users expect to work intuitively. The key is to use standard gestures that users already know and avoid inventing custom ones that require learning.
Touch targets should be at least 44×44 points (Apple) or 48×48 dp (Google). The thumb-reachable area on large screens is concentrated in the lower half, which is why primary actions should be placed there. Haptic (vibration) and visual (animation) feedback confirms actions and improves the perception of quality.
- Touch targets: minimum 44×44pt (iOS) or 48×48dp (Android)
- Thumb zone: frequent actions should sit in the lower half of the screen
- Feedback: every action needs visual, haptic or auditory confirmation
- Standard gestures: don’t reinvent interactions users already understand
Onboarding and first-run experience
25% of users abandon an app after a single use. Onboarding is your chance to demonstrate value before they leave. Best practices have shifted from explanatory screen carousels (which nobody reads) to progressive onboarding: teaching features in context, when the user needs them.
If the app requires sign-up, defer the data request until the user has experienced the product’s value (progressive profiling). Offering social login (Google, Apple Sign In) reduces friction dramatically. The first minute of use determines whether the app stays installed or gets deleted.
- Show value before asking for sign-up: let users explore before requiring an account
- Progressive onboarding: teach features in context, not in a pre-launch carousel
- Social login: Apple Sign In (mandatory on iOS if you offer social login) + Google
- Empty states: design blank screens as opportunities to guide the user
Platform conventions: iOS vs Android
iOS and Android have different design conventions that users on each platform expect to find. Apple’s Human Interface Guidelines emphasise transparency, San Francisco typography and back-swipe navigation from the left edge. Google’s Material Design uses elevation, FABs (Floating Action Buttons) and a bottom navigation bar.
Respecting these conventions does not mean designing two completely different apps. The balance lies in maintaining brand identity while adapting interaction patterns to what users expect on each platform. Apps like Airbnb and Spotify achieve a distinctive design that feels natural on both systems.
Accessibility in mobile apps
Accessibility is not an add-on; it’s a requirement. 15% of the global population has some form of disability. Moreover, accessibility benefits everyone: good contrast helps outdoors in sunlight, larger text helps older users, and captions help in noisy environments.
Both platforms offer robust assistive technologies: VoiceOver (iOS) and TalkBack (Android). For your app to work well with them, every interactive element needs a descriptive accessibility label, images need alt text, and navigation must follow a logical order.
- Minimum contrast: 4.5:1 ratio for normal text, 3:1 for large text (WCAG AA)
- Dynamic type: respect the system’s text size preferences
- Accessibility labels: describe the function of every interactive element
- High contrast and reduced motion modes: honour user preferences
Micro-interactions and visual feedback
Micro-interactions are the details that make an app feel polished: a button animation on press, the transition between screens, the bounce of a pull-to-refresh or the state change of a toggle. Although they seem superficial, they determine the perception of quality and professionalism.
Animations should be fast (200–300ms for transitions, 100ms for touch feedback), use natural easing (not linear) and be functional (not decorative). Excessive or slow animations create the feeling that the app is sluggish, even if actual performance is solid.
- Duration: 100ms for touch feedback, 200–300ms for screen transitions
- Easing: use ease-in-out curves for natural motion
- Purpose: every animation should communicate something (state, direction, hierarchy)
- Reduced motion: provide a static alternative for users with vestibular disorders
Key Takeaways
- The bottom tab bar is the most effective navigation pattern for most apps
- Touch targets should be at least 44×44pt and primary actions placed in the thumb zone
- Progressive onboarding beats explanatory carousels: teach in context
- Respect each platform’s conventions without losing brand identity
- Accessibility benefits all users, not just those with disabilities
- Micro-interactions define the perceived quality of the app
Want an app with outstanding user experience?
We design user-centred mobile applications with the patterns and conventions that maximise retention and satisfaction.