Oracle Visual Builder: Applications That Outlive Their First Release · Module 12 · Responsive and mobile
Lab briefing · Make one screen work on a phone
Lesson 126 of 176 · 3 min
Take the BUSIEST SCREEN you have built and MAKE IT USABLE AT 375 PIXELS without REMOVING ANYTHING A USER NEEDS. The two constraints are what make this a design exercise rather than a layout one: the width is fixed, and deleting the problem is not allowed. START BY OPENING IT AT 375 IN DEVICE EMULATION AND WRITING DOWN WHAT IS WRONG. Not fixing anything yet. The list is usually four or five items long and it is almost always the same list: a table too wide, a form whose important field is now far down, controls off the edge, something pinned to a side, and a page so long the action is below several screens. DO THE TABLE FIRST, BECAUSE IT IS THE ONE THAT CANNOT BE SOLVED BY LAYOUT. Decide the two or three values that identify a record — Lesson 3 — and make each row a card…
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.
In this module: Module 12 · Responsive and mobile
- 1Responsive, or a mobile application
- 2How the layout responds
- 3A table on a phone
- 4Touch, and what changes
- 5Testing at real sizes
- 6Right-to-left on a small screen
- 7What breaks: two mobile failures
- 8Lab briefing · Make one screen work on a phone