MSAMM
Back to course

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

What breaks: two mobile failures

Lesson 125 of 176 · 3 min

A TABLE THAT PUSHED ITS OWN CONTROLS OFF THE SCREEN, and AN APPLICATION SIGNED OFF ON A LAPTOP AND USED ENTIRELY ON PHONES. THE TABLE THAT PUSHED ITS CONTROLS OFF IS THE ONE WITH THE SHARPEST SYMPTOM. A wide table on a narrow screen widens the row beyond the viewport, and whatever sits at the end of that row — which is where the actions go — is off the edge. Lesson 3, and the page looks nearly right: the data is there, it scrolls, and the buttons are simply not reachable. WHICH MAKES THE PAGE READ-ONLY BY ACCIDENT. Every row is visible, no error appears, and the user cannot act on any of them. And the last element being unreachable is the pattern to remember, because the last element is nearly always the thing that does something — the action column, the submit, the menu trigger. AND THE APPLICATION

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