Building responsive React applications that survive real phones
Practical patterns for responsive React UI: mobile-first defaults, fluid type, and the checks that catch broken layouts before users do.
- React
- Responsive
- CSS
Most layouts don't break because a developer can't write CSS. They break because the design was decided on a 1440px monitor and then squeezed into a phone. Responsive work starts earlier than the media queries.
Start from the smallest screen
Write the single-column layout first, then add complexity as width allows. When you design desktop-first, every breakpoint becomes a patch on top of something that was already wrong at 320px.
- One column is the default; grids opt in at breakpoints.
- Navigation collapses into a menu by default, and desktop navigation is the enhancement.
- Type scales use clamp() so headings shrink smoothly instead of jumping between fixed sizes.
.title {
font-size: clamp(2.5rem, 6vw, 4.5rem);
line-height: 1.05;
}Components should own their responsiveness
Responsiveness scattered across a dozen files is impossible to maintain. A card component should know how it behaves at 320px, and its parent shouldn't need to patch it with overrides.
If you have to remember a magic parent class to make a component work on mobile, the component is broken — not the page.
The checks that actually catch bugs
- 1.Open the page at 320px and scroll the whole thing. Horizontal overflow hides in long words, images and tables.
- 2.Test real touch targets. Anything under roughly 44px will be mis-tapped.
- 3.Resize slowly between breakpoints. Jumps happen at the exact width where a grid switches columns.
- 4.Check long content — a name, a project title, an error message — not just the text you designed with.
In short
Responsive design is a default, not a pass you do at the end. Choose mobile-first layouts, let components own their behaviour, and verify at the widths your users actually visit.