Responsive & Adaptive UI Design Adapt the application shell and domain surfaces across real viewport pressure points
Phase 20 - Production Application UI Volume 06 - Professional Frontend
v
v
v
Phase 20 turns the secure full-stack foundation into a coherent, accessible application interface without moving business authority into the browser.
Responsive design is not “desktop, then shrink everything” TaskFlow uses layout changes at pressure points rather than device-name breakpoints. The shell collapses when the sidebar and content can no longer coexist comfortably; page actions stack when horizontal space becomes constrained.
<= 900px Desktop sidebar removed; mobile navigation available<= 640px Page header stacks; primary action becomes full widthUse modern viewport units carefully The shell uses `100dvh` so mobile browser chrome changes are handled better than a hard `100vh` assumption. But content should still be allowed to grow; avoid locking pages to viewport height when they contain long data.
Responsive test matrix • 320px narrow mobile
• 390px common mobile
• 768px tablet portrait
• 900px shell breakpoint
• 1024px laptop/tablet landscape
• 1366px common desktop
• 1920px wide desktop
If a table needs horizontal scrolling, contain it in the table region. A page-level scrollbar often indicates a broken layout constraint.
Authentication answers who the request represents. Treating decoded or client-supplied identity as trusted is a security boundary failure.
Restate the goal of “Responsive and Adaptive UI Design” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: credentials/session → token → verification → trusted identity → protected operation. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: TaskFlow responsive shell with navigation, workspace context, task screens, loading/empty/error states, and accessible interactions.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
const token = readBearerToken(request);
const claims = await verifier.verify(token);
request.user = {
id: claims.sub,
email: claims.email,
};Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Inspect whether a token exists, whether it is expired, which issuer/audience signed it, and what the API verifier expects.
Trust only verified server claims; never repair identity by accepting a client-sent user id.
Without copying the final source, create a second small scenario that applies “Responsive and Adaptive UI Design” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Create reusable primitives for page header, panel/card, empty state, loading skeleton, and error state.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Mobile layout treated as desktop squeezed smaller
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.