The point about how people can perceive skeletons differently and how that can affect the emotional impact is interesting, but it's not like the underlying prob

The point about how people can perceive skeletons differently and how that can affect the emotional impact is interesting, but it's not like the underlying problems have been solved, even the ones posited by the site: 1. When you looked at the Loading Spinner, did you know how much time remains to complete? 2. How much of the content has loaded? 3. How much remains to load? You don't know how much time loading your data will take, you don't know how much of it has been loaded and how much remains, at least most of the time. You probably aren't going to spend a bunch of resources on adding information about the sizes of all of your API endpoints (or even averages if you can't do per-request), aggregating all of the endpoints that might need to be hit for some component to be displayed and visualizing it. Most of the time, even the loading spinners can be an afterthought in the face of needing to implement whatever the business requirements are. That's also why the fake loading bars that get slower towards the end were popular for a while. In my mind, use whatever is easy and feels good to you; spinners, loading bars or even skeletons. Don't just leave your users hanging with no visual feedback. The rest is just details.