> I always end up doing is remove a bunch of spinners because you don't need a spinner when the page loads instantly
I always have to remind people to add spinners, just because it loads instantly on your developer machine with a fiber connection (if not talking to a local container even) doesn't mean it will in the real world. But spinners only show when actively fetching so if it's fast they only show for a split-second. It's the best of both worlds.
Yeah, I don't like the split second spinners. And I work on company internal apps so every user is generally on a good connection.
What I might do is just add a global spinner using tanstack query, what I don't like is having 50 different spinners for every little component. Makes the site feel janky and weird.
I just don't see the point unless it's loading for 5+ seconds. If it's faster than that then the user won't have time to wonder if it's stuck anyway. And I prefer to have one or very few requests, rather than 10+ different ones for a single page.
I always have to remind people to add spinners, just because it loads instantly on your developer machine with a fiber connection (if not talking to a local container even) doesn't mean it will in the real world. But spinners only show when actively fetching so if it's fast they only show for a split-second. It's the best of both worlds.