Local UI State, useState and Component Ownership Volume 06 - Professional Frontend | Phase 23
Keep ephemeral interaction state local Mobile navigation visibility, a disclosure panel, a temporary hover preview, and a non-shareable dialog tab usually belong to the smallest client component that needs them. Moving them to a global store makes them harder to reason about and couples unrelated parts of the tree.
Example "use client"
export function MobileNavigation() {
const [open, setOpen] = useState(false)return (
<>
<button onClick={() => setOpen(true)}>Menu</button>
{open && <MobileMenu onClose={() => setOpen(false)} />}
</>
)
}When to lift state If two sibling components must coordinate the same value, move that value to their closest common owner and pass data/actions downward. Do not immediately jump to Context.
TaskFlow examples • Table row hover -> row/table component.
• Selected rows for a bulk action -> Task table boundary.
• Shell mobile navigation -> shell client boundary.
• Global toast queue may justify a shared provider because many distant features publish messages.
Authorization decides what an authenticated identity may do to a specific resource. UI hiding is never a substitute for server-side enforcement.
Restate the goal of “Local UI State useState and Component Ownership” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: trusted identity → requested action → resource scope → policy decision → allow/deny. 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: A state ownership map for TaskFlow plus refactored examples removing redundant synchronized state.. 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 canEdit =
user.role === "ADMIN" ||
(user.role === "MEMBER" && task.ownerId === user.id);
if (!canEdit) throw new ForbiddenException();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.
Trace verified identity, role, resource owner/workspace, and policy inputs separately.
Add server-side resource authorization; UI visibility is only experience, never enforcement.
Without copying the final source, create a second small scenario that applies “Local UI State useState and Component Ownership” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Remove local copies of TanStack Query data and derive filtered/presentational values during render.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.URL and React state disagreeing about filters
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.