Client State and Server Data
Does the browser help the user complete the task while the server remains the source of truth? Keep authoritative data on the server and use client state only for interaction that the browser legitimately owns.
What You Will Be Able to Decide
- Explain client state and server data in product and business terms.
- Apply this decision: Keep authoritative data on the server and use client state only for interaction that the browser legitimately owns.
- Recognise this material risk: the interface shows stale or invented truth that disagrees with the underlying system.
- Use this review: Follow one subscription action through loading, stale data, a narrow viewport, and a failed request.
A founder is reviewing the browser-facing part of a product with a consultant or coding agent. This lesson gives you a concrete question to take into a build brief, proposal review, or product decision.
Does the browser help the user complete the task while the server remains the source of truth? The course example is A subscription dashboard for a small B2B service; use it to decide what evidence would justify the choice before a builder implements it.
What Does Client State and Server Data Mean for Your Product?
A founder is reviewing the browser-facing part of a product with a consultant or coding agent.
Use the illustrative service for this course (A subscription dashboard for a small B2B service) to make the choice concrete. Does the browser help the user complete the task while the server remains the source of truth?
Technical term
Client State and Server Data
Client state records temporary interface conditions, while server data is authoritative product information retrieved from or persisted by a backend.
How Should a Founder Use Client State and Server Data?
For a subscription dashboard for a small b2b service, ask what would happen if the interface shows stale or invented truth that disagrees with the underlying system.
For this decision, the useful standard is that the interface remains understandable, accessible, and dependable across realistic devices and data states.
- Decision: Keep authoritative data on the server and use client state only for interaction that the browser legitimately owns.
- Evidence to request: show that the interface remains understandable, accessible, and dependable across realistic devices and data states.
- Owner: name who will respond if the interface shows stale or invented truth that disagrees with the underlying system.
- Record the result in the frontend proposal and review notes.
- Practical review: Follow one subscription action through loading, stale data, a narrow viewport, and a failed request.
How Do You Choose an Approach to Client State and Server Data?
Does the browser help the user complete the task while the server remains the source of truth? Keep authoritative data on the server and use client state only for interaction that the browser legitimately owns.
The risk is that the interface shows stale or invented truth that disagrees with the underlying system. Compare a simpler option with the proposed one, including who will operate either choice.
- Describe the user or business outcome that must be protected.
- Identify the most credible failure and its consequence.
- Compare the simplest adequate approach with one realistic alternative.
- Set a review point for when the decision may need to change.
What Evidence Should You Accept for Client State and Server Data?
What Warning Signs Should You Look For?
- The proposal does not address this risk: the interface shows stale or invented truth that disagrees with the underlying system.
- Nobody can show whether the interface remains understandable, accessible, and dependable across realistic devices and data states.
- The decision has no named owner or review point.
What Should You Ask a Consultant?
- What changes for the user if we choose this approach to client state and server data?
- How have we reduced or accepted this risk: the interface shows stale or invented truth that disagrees with the underlying system.
- Can you demonstrate that the interface remains understandable, accessible, and dependable across realistic devices and data states?
- Who owns the result, and when will we reconsider it?
Key takeaway
Key Takeaway
Keep authoritative data on the server and use client state only for interaction that the browser legitimately owns. Ask for evidence against the specific risk: the interface shows stale or invented truth that disagrees with the underlying system.