Accepting selected projects for Q2 2024 Check availability
SERVER 02SYSTEM ONLINELAST SYNC: 03:17:44RSS_FEED.XML — PARSE WARNING
HALF ASSEDTECHNICAL NOTES_
EST. 2009ISSUE 04.2BEST VIEWED AT 1024 × 768
TECHNICAL NOTES / TECHNICAL NOTES / FRONT-END / RECORD 884719
[FRONT-END]NOTE

Choose responsive breakpoints from content

POSTED: 27.03.2014AUTHOR: ADMIN5 MIN READCOMMENTS: 0

A layout should change when its content no longer works, not when a list of popular devices says that a new category has begun.

Begin with the narrow layout

Place content in priority order and allow text, controls and media to use the available width. Increase the viewport until line length, grouping or unused space justifies a different arrangement.

Keep breakpoints local to behaviour

Navigation, data tables and card grids may need to change at different widths. Avoid one global phone-tablet-desktop set that forces unrelated components to adopt the same transition.

Test the spaces between devices

Resize continuously, zoom text and use long content rather than checking only named handset dimensions. New devices then fall into a layout governed by available space instead of an incomplete model list.

LAYOUT PRINCIPLE

The breakpoint is evidence of content pressure, not a claim that a particular device is 768 pixels wide.