Lazy-loaded routes, a functional guard that remembers where you were going, and data resolved before the component renders.
See alsoRoutes and guards, the React wayThe same problems in React — lazy routes, an Outlet guard, and a loader.
A signed-out visitor to /sprints lands on sign-in and is returned afterwards; the sprint page never renders empty.
Published in full, before you start — every point is one of these and there is nothing else.
Standalone components declare what they need instead of belonging to an NgModule, and inject() gets a dependency without a constructor parameter — together they are most of what changed in modern Angular.
Authentication is who you are; authorization is what you are allowed to do. Policies keep that rule in one place instead of scattered if-statements.
Anything that talks to a network can be slow or fail; a screen with no loading state and no error state is a screen that looks broken the first time the wifi drops.
Network calls fail. Code that assumes they succeed turns a slow connection into a blank screen with no explanation.