The article shows how to eliminate per-component spinners by moving data fetching into route loaders and preloading that data on hover or intersection. Route transitions then delay navigation until all required data is ready, making pages appear fully rendered instantly. A single global loading indicator handles only cases where data truly takes too long or on full page refresh.

The article argues that instead of sprinkling spinners and skeletons throughout components, you can shift data fetching to route-level loaders and preload data on hover or in-view before navigation. Using route transitions lets you delay committing a route change until all required data is ready, keeping the app fast and eliminating most loading UI. A global fallback indicator covers refreshes or genuinely slow loads, while blank spots during development highlight missed preloads.