Design, before Any SoftwareLesson 58 of 74

Module 6 · Real screens, real thumbs, real paper

Breakpoints come from the content, not from devices

In this lesson

  • 8 min read
  • 6 reading sections
  • Knowledge check
  • Lesson 3 of 10 in this chapter

This chapter’s goalProduce a layout that works at 360 CSS pixels one-handed in daylight, at 400% zoom, and on paper with correct bleed and resolution, naming for each constraint the specific number it imposes and which design decisions change because of it.

This chapter’s media

The film explains chapter ideas. The audiobook narrates the complete teaching text.

FormatEnglishहिंदी
Chapter filmWatch1:49Not available
Full audiobookNot availableNot available

A little at a time

Explore an idea, try it, then check what stays.

Step 1 of 8Free · no account needed
Lesson steps

Naming breakpoints after phones ages badly

A stylesheet with $tablet: 768px was written when there was a tablet at 768 pixels. There are now devices at every width from 320 to 3840, foldables that change width mid-session, split-screen multitasking, and browser windows people resize for no reason.

The method that does not age: widen and narrow the browser slowly, and put a breakpoint wherever the layout stops working. Not where a device sits. Where your content breaks.

This produces breakpoints at odd numbers (540, 720, 960, 1180) and that is the sign you did it right. Round numbers usually mean somebody copied them.

Your place and first choices stay on this browser. Classroom credit is recorded separately.

Stuck on something?Ask Meher, your AI tutor

How to cite: Addaly (2026) ‘Breakpoints come from the content, not from devices’, in Design, before Any Software. Edited by M. Mun. Addaly. Available at: https://addaly.com/learn/design-foundations/breakpoints-from-content (Accessed: 21 November 2026).