01 · cover
Day 5 · Week 1
The Capable Surface
Where the interface stops being decoration and starts being the product
Open cold. Ask who shipped something yesterday that a user could actually touch.
02 · section
Part one
What the user can reach
03 · title-body
Framing
A surface is a promise you have to keep
Every control you put on screen is a commitment: this will work, it will work quickly, and it will tell you the truth when it does not. Most teams ship the control and negotiate the promise later. By Friday you will have built three surfaces that keep their promise under load, offline, and in Arabic — because a UAE product that only works in English on good wifi is a demo, not a product.
The offline case is the one they underestimate. Push on it.
04 · bullets
Today
Five things we build before lunch
- 01 A form that survives a dropped connection mid-submit
- 02 An empty state that tells the user what to do next
- 03 A loading state nobody notices
- 04 An error that names the cause, not the stack trace
- 05 An Arabic layout that was not an afterthought
Time-box each to 25 minutes. Demo round after the third.
05 · image-left
Case study
A ministry portal that lost 40% of applicants at step three
The form worked. The validation was correct. Applicants still left — because step three asked for an Emirates ID scan with no indication that the previous two steps had been saved.
- — Nothing was broken; trust was
- — One line of copy recovered most of the drop
- — Instrumentation found it, not a redesign
Numbers are illustrative — do not attribute to a named entity.
06 · statement
The interface is not the last 10% of the work. It is the only part of the work your user will ever see.
UAEN Full-Stack AI · Day 5
Hold the slide. Do not talk over it.