Skip to content
NewTemplates & toolkits are on the way — join the waitlist
Hecham Gazhi

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-width media queries add complexity.
Examplecss
.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:

RangeTypical devicesTypical grid
< 640pxPhones4 columns, 16px margins
640–1023pxLarge phones, tablets8 columns, 24–32px margins
1024–1279pxSmall laptops, landscape tablets12 columns
≥ 1280pxDesktops12 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

PatternWhat changesExample
ReflowColumns stack vertically3 cards in a row → 1 per row
Reveal / hideSecondary content is hidden or movedSidebar becomes a drawer
ResizeElements scale fluidlyHero image fills width
RepositionElements move to a better placeFilters move into a bottom sheet
TransformA component becomes a different oneTabs → 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.
GuidelineMinimum target
Apple Human Interface Guidelines44 × 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

PatternProsCons
Bottom tab barAlways visible, easy to reach, shows current locationOnly 3–5 items
Hamburger menuHolds many items, saves spaceHidden navigation is used less
Top tabsGood for switching views within a sectionHard to reach; limited items
Bottom sheetReachable, contextualCan hide content behind it
Floating action buttonHighlights one main actionCan 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

  1. Pick a desktop dashboard or product listing page.
  2. Rank its content and actions by importance.
  3. Design the 375px mobile version: what reflows, what moves to a drawer or bottom sheet, what transforms?
  4. Check every tap target is at least 44×44 and the main action is in the thumb zone.
  5. Design the 768px tablet version in between.

Test yourself

Responsive & mobile UI quiz

5 questions. Score 70% or more to complete the lesson.

  1. 1.Apple's recommended minimum touch target is…
  2. 2.What does 'mobile-first' mean?
  3. 3.Breakpoints should be chosen based on…
  4. 4.Turning a data table into stacked cards on mobile is which adaptation pattern?
  5. 5.Why put primary navigation in a bottom tab bar on mobile?