Custom frontend routes and screens

A custom frontend feature has two separate owners. The screen owns query, mutation, and interaction state. The application shell owns URL registration, navigation, public or protected placement, and page layout.

• Custom workflow screens covers generated reads, typed actions, bounded projections, loading and error states, and cache refresh.
• Frontend routes, navigation, and layout covers App.tsx, shell page composition, protected and public routes, navigation entries, reload, and responsive checks.

A protected frontend route is a UX boundary. The generated table routes and application endpoint must still enforce authentication, abilities, and row scope on the server.

Related documentation

• Cached table reads and refresh
• Typed API clients
• App shell, routes, and navigation