Oracle Visual Builder: Applications That Outlive Their First Release · Module 7 · Binding data to the page
Empty, loading and error states
Lesson 75 of 176 · 3 min
The three states EVERY SCREEN HAS and MOST DESIGNS IGNORE. What each should say, and why "NO RESULTS" MUST NOT BE SHOWN WHEN A CALL FAILED. Every screen that loads data has four states and designs almost always describe one of them — the one where everything worked. LOADING IS THE ONE PEOPLE SKIP BECAUSE IT IS BRIEF ON THEIR MACHINE. On a slow connection it is several seconds of a page that looks finished and empty, so a user concludes there is nothing and leaves. Anything is better than nothing here — a spinner, a skeleton, a line of text — because the message is "wait", and silence says "done". EMPTY IS AN ANSWER AND SHOULD READ AS ONE. "No orders match this filter" is useful; a blank rectangle is indistinguishable from a broken page. And it should say what to do next where there is something — clear…
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 7 · Binding data to the page
- 1Binding, and what the framework does for you
- 2Tables and lists
- 3Forms and two-way binding
- 4Formatting: dates, numbers and currency
- 5Arabic and right-to-leftFree preview
- 6Conditional display
- 7Sorting, filtering and searching
- 8Empty, loading and error states
- 9What breaks: three binding failures
- 10Lab briefing · One screen, every state