Learning on Web Dev Open is free for all.

Framework Internals > The App Router, and where the seams areBuild the thing, properly
Phase 04The App Router, and where the seams are230 of 434

Build the thing, properly

Something with real data, real mutations and real auth, where every rendering decision is one you can defend.

Solo project240 minAI implements

Done when

  • At least three routes using different rendering strategies, each justified in the README
  • Mutations invalidate exactly what they affect and nothing more
  • Every screen has a designed empty, loading and error state that does not shift the layout
  • Authorisation is enforced inside every server action, not only in the UI
  • No "use client" above a component that genuinely needs interactivity

Nobody marks this for you. It goes into your phase checkpoint, where a person does.

You should now be able to

  • Ship an application with a defensible rendering decision per route
  • Handle every state of every screen you built
Ask the community

Loading…

← PreviousReading a framework from its sourceThe App Router, and where the seams areNext →Audit your own boundariesThe App Router, and where the seams are