What the Frontend Actually Does
The frontend presents product information and controls while coordinating navigation, local state, validation, accessibility, and communication with backend services. 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.
- Ask a consultant for evidence rather than reassurance.
A founder is reviewing the browser-facing part of a product with a consultant or coding agent.
The frontend presents product information and controls while coordinating navigation, local state, validation, accessibility, and communication with backend services.
A consultant can recommend and implement the technical approach. The founder still needs to decide which outcome matters, which risk is acceptable, and what evidence is sufficient.
The Founder Situation
A founder is reviewing the browser-facing part of a product with a consultant or coding agent.
The immediate question is what the frontend actually does. The technical label matters only because it changes a product decision, a responsibility, or the evidence required before launch.
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.
Treat it like a clause in a commercial agreement: its value comes from making expectations and consequences clear, not from sounding formal.
What Matters in Practice
Start with the product consequence, then choose the simplest technical treatment that protects it. A longer tool list is not a stronger plan.
For this decision, the useful standard is that the interface remains understandable, accessible, and dependable across realistic devices and data states.
- Make the decision explicit: Define which responsibilities belong in the browser and which rules must remain enforced by the backend.
- Ask what evidence would show that the chosen approach works.
- Name the person or provider responsible when the approach fails.
- Record the result in the frontend proposal and review notes.
A Proportionate Decision
Define which responsibilities belong in the browser and which rules must remain enforced by the backend.
The principal risk is that important business or permission rules are trusted to code that users can bypass or alter. This does not require the most expensive possible solution. It requires the consequence to be understood and the control to match it.
- 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.
Strong Evidence and Weak Reassurance
Warning Signs
- Nobody can explain how what the frontend actually does changes a user or business outcome.
- The proposal does not address this risk: important business or permission rules are trusted to code that users can bypass or alter.
- The only evidence is a successful demonstration of the easiest path.
- The decision has no named owner, boundary, or review point.
- A provider-specific feature is being mistaken for a permanent product requirement.
Questions to Ask a Consultant
- What decision are we making about what the frontend actually does?
- Which user or business outcome does the recommendation protect?
- How have we reduced or accepted this risk: important business or permission rules are trusted to code that users can bypass or alter.
- What evidence can I review without relying on the original implementer?
- What is deliberately deferred, and when will it be reconsidered?
- Who owns the accounts, data, documentation, and recovery process?
Key takeaway
Key Takeaway
The frontend presents product information and controls while coordinating navigation, local state, validation, accessibility, and communication with backend services. The founder's job is to make the consequence explicit; the consultant's job is to recommend and demonstrate a proportionate implementation.