Progressive DisclosureLocation preview expands to full details
Thumb ZoneAll controls at bottom of screen
Snap PointsThree distinct sheet heights
Key insight: Google Maps pioneered the multi-height bottom sheet pattern now used everywhere.
Swipe Actions
Archive, Flag, Delete
Principles Identified:
Hidden PowerSecondary actions revealed on swipe
Visual HintsPartial swipe shows what's available
Undo SafetyAccidental deletes can be undone
Key insight: iOS Mail's swipe-to-reveal pattern became standard for list-based apps.
Bottom Navigation
5 core actions
Principles Identified:
Thumb ZoneAll primary navigation at bottom
RecognitionIcons immediately recognizable
Visual FocusContent area maximized
Key insight: Instagram keeps the main navigation bar in constant thumb reach for easy switching.
Part E
Common Failures
12
Mobile Design Mistakes
Common errors that hurt mobile usability.
Failure: Tiny Touch Targets
Hard to tap
Fix: Minimum 44×44pt tap areas
Easy to tap
Rule: 44×44pt minimum for all interactive elements. Visual can be smaller—expand tap area with padding.
Failure: Hamburger for Primary Actions
☰
Hidden in corner, hard to reach
Fix: Use visible bottom navigation
🏠🔍➕👤
Visible, in thumb zone
Rule: Hamburger menus hide navigation and force awkward reaches. Use visible bottom tabs for primary actions.
Failure: Ignoring Safe Areas
Button behind notch
Hidden by device cutouts
Fix: Use env(safe-area-inset-*)
Button in safe area
Visible and tappable
Rule: Use CSS env(safe-area-inset-*) to pad content away from notches and home indicators.
Failure: Desktop Hover States on Mobile
Tooltip on hover
No hover on touch!
Fix: Use touch-appropriate feedback
Long-press for info
Touch-appropriate
Rule: Mobile has no hover state. Replace hover tooltips with long-press, info icons, or inline text.
Quick Test
Can you use your app entirely with one thumb? Try holding your phone normally and reaching every interactive element.
Part F
Visual Tests
13
Mobile Usability Testing
Validate your mobile design works for real users.
01
Thumb Zone Test
Tests: Reachability
Hold your phone one-handed. Can your thumb reach all primary actions without shifting grip? Frequent actions should be in the comfortable zone (bottom center).
Hold phone normally
Try reaching every button
Note difficult areas
02
Touch Target Audit
Tests: Tap accuracy
Using browser DevTools, measure all interactive elements. Anything below 44×44pt (or 48×48dp on Android) needs larger tap areas.
☑ Buttons: 44pt+ ✓
☑ Links: 44pt height ✓
☑ Icons: 44pt tap area ✓
03
Safe Area Check
Tests: Content visibility
Test on actual devices with notches (iPhone X+, many Android). Check landscape too. Is any content hidden behind notches, rounded corners, or home indicators?
Test on real devices
Both orientations
Check all edges
04
Gesture Discoverability
Tests: Hidden features
Have a new user try your app. Do they discover swipe actions and gestures? If important features are hidden behind gestures, add visual hints.
5-second test
Did user find swipe?
Add hints if not
Tools
Real devices (not just simulators), Chrome DevTools mobile emulation, Lighthouse accessibility audit.
/* Remove 300ms tap delay */
html {
touch-action: manipulation;
}
/* Active state feedback */
.button:active {
transform: scale(0.95);
opacity: 0.9;
}
/* Prevent text selection on buttons */
.button {
-webkit-user-select: none;
user-select: none;
-webkit-tap-highlight-color: transparent;
}
Touch Feedback via CSS
touch-action: manipulation - Removes 300ms delay
:active for feedback - Immediate visual response
tap-highlight-color - Removes default blue highlight
Tip: Fast tap feedback is critical—use :active instead of relying on :hover.
Mobile CSS Checklist
Touch targets 44pt+, safe area padding, touch-action: manipulation, :active feedback.
Part H
Self-Assessment
15
Self-Assessment
Test your understanding of mobile design patterns.
Q1
What is the minimum recommended touch target size?
Click to reveal
Answer: Apple recommends 44×44 points, Google recommends 48×48 dp. This accounts for average fingertip size (7-10mm) plus aiming error. The visual element can be smaller—expand the tap area with padding.
Q2
What is the 'thumb zone' and why does it matter?
Click to reveal
Answer: The thumb zone is the arc a thumb can comfortably reach when holding a phone one-handed. Bottom center is easiest; top corners are hardest. Since 49% of people use phones one-handed, frequent actions should be in the easy zone.
Q3
Why use bottom sheets instead of centered modals on mobile?
Click to reveal
Answer: Bottom sheets keep content in thumb reach. Centered modals put dismiss buttons at top corners—the hardest area to reach. Bottom sheets also allow multiple heights (peek/half/full) for progressive disclosure.
Q4
What are safe areas and how do you handle them in CSS?
Click to reveal
Answer: Safe areas are regions not obscured by notches, rounded corners, or home indicators. Use CSS env(safe-area-inset-*) variables to pad content away from these areas. Critical for fixed elements at screen edges.
Q5
How do you provide feedback for touch interactions?
Click to reveal
Answer: Use :active state (not :hover—mobile has no hover). Add touch-action: manipulation to remove 300ms tap delay. Use transform: scale() or opacity for immediate visual feedback. Remove default tap highlight with -webkit-tap-highlight-color: transparent.