What the Frontend Actually Does
Does the browser help the user complete the task while the server remains the source of truth? Define which responsibilities belong in the browser and which rules must remain enforced by the backend.
What You Will Be Able to Decide
- Explain what the frontend actually does in product and business terms.
- Apply this decision: Define which responsibilities belong in the browser and which rules must remain enforced by the backend.
- Recognise this material risk: important business or permission rules are trusted to code that users can bypass or alter.
- 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 What the Frontend Actually Does 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
What the Frontend Actually Does
The frontend presents product information and controls while coordinating navigation, local state, validation, accessibility, and communication with backend services.
How Should a Founder Use What the Frontend Actually Does?
For a subscription dashboard for a small b2b service, ask what would happen if important business or permission rules are trusted to code that users can bypass or alter.
For this decision, the useful standard is that the interface remains understandable, accessible, and dependable across realistic devices and data states.
- Decision: Define which responsibilities belong in the browser and which rules must remain enforced by the backend.
- Evidence to request: show that the interface remains understandable, accessible, and dependable across realistic devices and data states.
- Owner: name who will respond if important business or permission rules are trusted to code that users can bypass or alter.
- 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 What the Frontend Actually Does?
Does the browser help the user complete the task while the server remains the source of truth? Define which responsibilities belong in the browser and which rules must remain enforced by the backend.
The risk is that important business or permission rules are trusted to code that users can bypass or alter. 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 What the Frontend Actually Does?
What Warning Signs Should You Look For?
- The proposal does not address this risk: important business or permission rules are trusted to code that users can bypass or alter.
- 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 what the frontend actually does?
- How have we reduced or accepted this risk: important business or permission rules are trusted to code that users can bypass or alter.
- 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
Define which responsibilities belong in the browser and which rules must remain enforced by the backend. Ask for evidence against the specific risk: important business or permission rules are trusted to code that users can bypass or alter.