MSAMM
Back to course

Oracle Visual Builder: Applications That Outlive Their First Release · Module 12 · Responsive and mobile

Testing at real sizes

Lesson 123 of 176 · 3 min

A NARROW BROWSER WINDOW IS NOT A PHONE. What to use, and THE LAYOUT THAT BROKE ONLY AT THE BREAKPOINT. Almost everybody tests responsiveness by dragging the window narrower, and it misses several whole classes of defect. THE FIRST DIFFERENCE IS THE SCROLLBAR. A desktop window has one and a phone does not, so a narrow window is about ten pixels narrower than it reports — and a layout that just fits in a resized window may overflow on the device. An overflow of a few pixels in a resized window is frequently the scrollbar and frequently is not, and you cannot tell which without the device. THE SECOND IS TOUCH. A resized window still has a mouse, so hover still works, targets are still hit precisely, and every defect in Lesson 4 is invisible. The layout is what a narrow window tests; usability is not. SO USE THE BROWSER'S

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Visual Builder: Applications That Outlive Their First Release, with a certificate on completion and a fourteen-day refund window.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 12 · Responsive and mobile

  1. 1Responsive, or a mobile application
  2. 2How the layout responds
  3. 3A table on a phone
  4. 4Touch, and what changes
  5. 5Testing at real sizes
  6. 6Right-to-left on a small screen
  7. 7What breaks: two mobile failures
  8. 8Lab briefing · Make one screen work on a phone