Skeletons are extremely hard to get right. The system must quickly predict what part of the app is about to load and render the appropriate skeleton. If you mak

Skeletons are extremely hard to get right. The system must quickly predict what part of the app is about to load and render the appropriate skeleton. If you make a mistake, or crash, or redirect incorrectly, then you might end up showing a blank screen or something even worse than a spinner. Any screen that doesn't fit an existing layout must have a separate (set) of skeletons created, because showing a mismatching skeleton is very confusing. All this stuff has to account for different devices, as usual. It's almost like maintaining a parallel set of minimalistic designs. It's doable, but only if you have enough resources or if your app is very simple.