UI Design · Lesson 09 / 12
Responsive & mobile UI
Designing for every screen: mobile-first thinking, breakpoints, fluid layouts and adaptation patterns, touch targets, thumb zones, mobile navigation, platform conventions and testing on real devices.
5 min read · 5 quiz questions
Why responsive design
People use products on phones, tablets, laptops, large monitors and everything in between — often switching devices for the same task. Globally, more web traffic now comes from mobile devices than from desktops. Responsive design means one product adapts its layout, content and interactions to the screen and input method in use.
It's not just about squeezing a desktop design into a narrow screen. Mobile users have different contexts: one hand, small screen, touch input, interruptions, sometimes slow connections.
Mobile-first
Mobile-first means designing the smallest screen first, then enhancing the layout as space increases. It forces you to decide what's essential, because there's no room for anything else.
- Start with the core content and the main action.
- Add secondary content, sidebars and extra columns as the screen grows.
- In CSS, base styles target mobile and
min-widthmedia queries add complexity.
.products { display: grid; grid-template-columns: 1fr; gap: 16px; }
@media (min-width: 640px) { .products { grid-template-columns: repeat(2, 1fr); } }
@media (min-width: 1024px) { .products { grid-template-columns: repeat(3, 1fr); gap: 24px; } }
@media (min-width: 1280px) { .products { grid-template-columns: repeat(4, 1fr); } }Breakpoints
Breakpoints are widths where the layout changes. Choose them based on where your content starts to look awkward, not on specific device models. Common ranges:
| Range | Typical devices | Typical grid |
|---|---|---|
| < 640px | Phones | 4 columns, 16px margins |
| 640–1023px | Large phones, tablets | 8 columns, 24–32px margins |
| 1024–1279px | Small laptops, landscape tablets | 12 columns |
| ≥ 1280px | Desktops | 12 columns, max content width |
Design at least three key sizes (e.g. 375px, 768px and 1440px wide) and check the in-between sizes too — layouts often break at 900px, not at your breakpoints.
Adaptation patterns
| Pattern | What changes | Example |
|---|---|---|
| Reflow | Columns stack vertically | 3 cards in a row → 1 per row |
| Reveal / hide | Secondary content is hidden or moved | Sidebar becomes a drawer |
| Resize | Elements scale fluidly | Hero image fills width |
| Reposition | Elements move to a better place | Filters move into a bottom sheet |
| Transform | A component becomes a different one | Tabs → dropdown; table → cards |
Common mistake: Hiding important content or features on mobile. Mobile users often need everything desktop users need — design a different arrangement, not a reduced product.
Touch targets
Fingers are much less precise than mouse pointers. Small targets lead to mis-taps and frustration.
- The visible element can be smaller as long as the tappable area meets the minimum.
- Leave at least 8px between adjacent targets.
- Make whole rows or cards tappable, not just a small arrow or text link.
| Guideline | Minimum target |
|---|---|
| Apple Human Interface Guidelines | 44 × 44 pt |
| Material Design (Android) | 48 × 48 dp |
| WCAG 2.2 (Level AA, 2.5.8) | 24 × 24 CSS px (with some exceptions) |
Thumb zones and reachability
Most people hold their phone in one hand and tap with the thumb at least some of the time. On large phones, the top corners are hard to reach. Research by Steven Hoober on how people hold phones popularised the idea of thumb zones: easy to reach near the bottom centre, harder at the top.
- Put primary navigation in a bottom tab bar (3–5 items) on mobile apps.
- Use bottom sheets for actions and filters.
- Place the main action (Add to cart, Send) where the thumb can reach it — often a sticky bar at the bottom.
- Keep destructive actions away from easy-tap areas.
Mobile navigation patterns
| Pattern | Pros | Cons |
|---|---|---|
| Bottom tab bar | Always visible, easy to reach, shows current location | Only 3–5 items |
| Hamburger menu | Holds many items, saves space | Hidden navigation is used less |
| Top tabs | Good for switching views within a section | Hard to reach; limited items |
| Bottom sheet | Reachable, contextual | Can hide content behind it |
| Floating action button | Highlights one main action | Can cover content; one action only |
Platform conventions
Native apps should respect the conventions of their platform — users expect them (Jakob's law).
- iOS: back navigation at top-left plus swipe-from-edge to go back; tab bar at the bottom; SF Pro font; large titles.
- Android: system back gesture/button; Material components; Roboto or the brand font; top app bar.
- Web on mobile: respect browser UI, safe areas (notches), and avoid fixed elements that cover content when the keyboard opens.
- Use the correct keyboard for each input (
type="email",inputmode="numeric").
There's no hover on touch screens. Never hide essential information or actions behind hover states — tooltips and hover menus need a tap alternative.
Performance and context
- Mobile connections can be slow or unstable — optimise images and show skeleton screens while loading.
- Design for interruption: save progress automatically, keep forms short.
- Support both portrait and landscape where it makes sense.
- Respect system settings: text size (Dynamic Type), dark mode, reduced motion.
- Always test on real devices, not just a resized browser — touch, text size and performance feel very different.
Key takeaways
- Responsive design adapts layout, content and interaction to each screen and input method.
- Design mobile-first and choose breakpoints where content breaks, not by device.
- Use reflow, reveal, resize, reposition and transform patterns — don't hide important features.
- Touch targets: at least 44×44pt (iOS) or 48×48dp (Android); place key actions within thumb reach.
- Follow platform conventions, never rely on hover, and test on real devices.
Exercise
Make a desktop screen mobile
- Pick a desktop dashboard or product listing page.
- Rank its content and actions by importance.
- Design the 375px mobile version: what reflows, what moves to a drawer or bottom sheet, what transforms?
- Check every tap target is at least 44×44 and the main action is in the thumb zone.
- Design the 768px tablet version in between.
Test yourself
Responsive & mobile UI quiz
5 questions. Score 70% or more to complete the lesson.
