4 ms·
You want to know why they exist? Because of Google Core Web Vitals metrics! CLS (Cumulative Layout Shift) can go to zero if you place proper skeletons. I stil
by Raed667 5y ago
You want to know why they exist? Because of Google Core Web Vitals metrics!
CLS (Cumulative Layout Shift) can go to zero if you place proper skeletons.
I still prefer it to content jumping around when the API response is done.
- deleted 5y ago[deleted]
- Zababa 5y agoThis is a really good solution to a problem that shouldn't even exist.
- phist_mcgee 5y agoSlow APIs? Good luck eradicating those
- noisem4ker 5y agoWell, they definitely don't solve the problem for the user, as the grey boxes inevitably aren't the same shape as the content that eventually appears, and the jumping around is still there. Text fields are often variable length and can reflow. Buttons are also frequently dynamic, and all sorts of widgets may not just line up. Sometimes, incomprehensive design changes cause further disalignment between the skeleton and the actual content. It's sad and funny that the YouTube app seems to have just recently jumped on this bandwagon (either that, or the situation worsened so much that I started noticing how bad it is).
- Raed667 5y agoI agree with you that snapping some skeletons on a UI and calling it a day won't help the user This is why I sneaked this part in: > if you place proper skeletons I had to work on this recently and unless you take the design constraints seriously you will eventually end up in the situation you described.