MSAMM
Back to course

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

A table on a phone

Lesson 121 of 176 · 3 min

The commonest problem in this module. What to do instead, and WHY SHRINKING IT IS NOT ONE OF THE OPTIONS. Business applications are made of tables and tables are the one component that does not survive a narrow screen, which makes this the defining problem of mobile in this product. THE REASON IS ARITHMETIC RATHER THAN DESIGN. Eight columns need a certain width to be readable, and a phone does not have it. Nothing about layout can create space that is not there. SO SHRINKING IS NOT AN OPTION BECAUSE IT PRODUCES SOMETHING UNREADABLE OR UNTAPPABLE. Smaller text on a device held at arm's length, and touch targets below the size a finger can hit — Lesson 4. It renders, it fits, and it cannot be used, which is the worst of the available outcomes because it looks like a solution. HORIZONTAL SCROLLING IS THE SECOND NON-ANSWER AND IT IS

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