Frontend Scope & Backend Boundaries
A precise map of what Nexus demonstrates in the browser and what your production backend must provide.
On this page 4
What you will learn
- Identify demo-only behavior.
- Plan backend responsibilities.
- Avoid mistaking UI state for persistence.
Browser responsibilities
Nexus supplies interface rendering, responsive behavior, client interactions, theme preferences, and example state transitions.
- Display API data.
- Collect and validate user input.
- Show loading, empty, error, and success states.
- Send authenticated requests to your service.
Server responsibilities
Your application architecture must supply every trusted operation.
- User identity, sessions, password policy, and account recovery.
- Authorization for every record and action.
- Database schema, migrations, queries, and transactions.
- Input validation at the server boundary.
- File storage, email, payments, queues, and scheduled jobs.
- Audit logs, secrets, monitoring, backup, and recovery.
Demo state is temporary
Local arrays, useState, localStorage, and hard-coded chart data are useful for presentation but do not provide shared, durable, or secure data.