MSAMM
Back to course

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

Touch, and what changes

Lesson 122 of 176 · 3 min

TARGETS, GESTURES AND THE HOVER STATE THAT DOES NOT EXIST. Small things that MAKE AN APPLICATION FEEL WRONG. None of these breaks anything. Together they are the difference between an application that works on a phone and one that is unpleasant on a phone, and users describe the second as broken. TARGETS ARE THE MEASURABLE ONE. A pointer is a pixel and a fingertip is not, so a control sized for a mouse is a control people miss — and the failure is worse than nothing happening, because missing frequently means hitting the thing beside it. Give anything tappable real size and real space around it, especially in a table row where several actions sit together. HOVER IS THE ONE THAT SILENTLY REMOVES INFORMATION. There is no hover on a touch screen, so anything revealed by hovering is not revealed at all — a tooltip explaining a column, an action

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