Versions Compared

Old Version 6

changes.mady.by.user Adam Butterworth

Saved on

compared with

New Version Current

changes.mady.by.user Adam Butterworth

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Expand
titleHow did these sizes get chosen?

The data driving these decisions lives in an edx internal spreadsheet here: https://docs.google.com/spreadsheets/d/1lhcnDo1Zsd7eWCP3_hz5oAHyYRB9ShCKgrEV0W6FLdU/edit#gid=908214725.

Goals behind the choices below:

  1. Keep the number of target sizes as small as possible.

  2. Target sizes that align with the largest segments of traffic.

  3. Create target sizes that make it more likely for us to create designs that work at 320 pixels wide (an a11y requirement).

  4. Avoid creating unnecessary work by splitting target screen sizes into tiers of attention.

...

Tier 1: Our primary sizes in design

  • 360 x 560

  • 1350 x 630650

Other primary concerns

Note

QA design or implementation at 320 pixels wide in scenarios likely to have issues.

If you are creating control bars or navigation bars that place buttons or fields on the left and right side of the viewport you should check your design at 320 pixels wide. You can preview an iPhone SE 1 in Chrome Dev Tools: Open Dev Tools, Turn on the Responsive viewport tool

...

Tier 2: Design for these sizes if it seems necessary

  • 320 x 450 This is the minimum width we must support to ensure our product is accessible.

  • 414 x 720

  • 1020 x 650

  • 1520 x 720

...