Build the TaskFlow Production UI Assemble the protected shell, real Task data and polished route states
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.
Build the first coherent TaskFlow product surface This book brings the pieces together into a route that feels like a real internal SaaS product: protected shell, page hierarchy, server-fetched authorized data, accessible table, status presentation, empty/loading/error states, and responsive behavior.
Target route tree (app)/ ■■■ layout.tsx ■■■ dashboard/page.tsx ■■■ projects/page.tsx ■■■ tasks/ ■■■ page.tsx ■■■ loading.tsx ■■■ error.tsx ■■■ not-found.tsx
components/ ■■■ app-shell/ ■■■ mobile/ ■■■ tasks/ ■■■ ui/
Page composition Figure 1 - `/tasks` rendering
v
v
Next.js calls NestJS `/tasks`
v
v
v
This is the payoff of the earlier backend phases: the UI can remain comparatively simple because the server contracts are strong.
The page header • Eyebrow/context label.
• One clear h1.
• Short purpose/description.
• Primary action positioned consistently.
The task list • Task title is the row link.
• Status is readable text plus color.
• Priority is visible without opening the record.
• Assignee and due date help scanning.
• No unauthorized task rows are fetched into the page.
Charts should answer a real operational question. We will add analytics when the domain has meaningful metrics rather than decorating the home page with arbitrary graphs.
Deployment is the controlled movement of a versioned artifact into a configured runtime with evidence of health and a credible rollback path.
Restate the goal of “Build the TaskFlow Production UI” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: versioned artifact → production config → runtime → health/smoke test → rollback path. 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.
1. Build an immutable artifact.
2. Apply production configuration/secrets.
3. Run compatible migrations.
4. Start the new version.
5. Check readiness and smoke tests.
6. Observe errors/latency.
7. Promote or execute rollback.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.
Separate platform deploy status from application readiness; run smoke tests against real routes and dependencies.
Use expand/contract migrations and keep rollback compatibility explicit before release.
Without copying the final source, create a second small scenario that applies “Build the TaskFlow Production UI” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Test keyboard focus, labels, landmarks, reduced-motion expectations, and narrow widths.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Clickable divs without keyboard semantics
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.