How do you build a project dashboard from persisted data?

How do you build a project dashboard from persisted data?

A project dashboard should reflect the backend’s saved records. Local sample data is useful during design but must not be confused with the user’s actual project history.

Fetch within the user’s scope

Use an authenticated endpoint that returns only permitted projects. Define ordering and pagination, and show appropriate loading and empty states. Display saved status and timestamps rather than inventing progress from how long the page has been open.

Keep mutations consistent

After creation or deletion, reconcile the list with the confirmed backend result. Handle failed updates without silently removing a valid project or showing a duplicate card. Test two accounts, an empty account, multiple pages, and a reload after a change. Include long titles and missing thumbnails so layout checks cover realistic records. A dashboard is complete when users can reliably find and reopen their saved work.