4 ms·
In my products one way I've tried to fix the UI jumping around when a separate network call responds is to add a facebook-style "shimmer" view while it loads. B
by downWidOutaFite 5y ago
In my products one way I've tried to fix the UI jumping around when a separate network call responds is to add a facebook-style "shimmer" view while it loads. But that doesn't work when the box might be hidden based on the network response.
- tuan 5y agoAnother approach is to show the box further down the page (the part of the page that is not yet visible on the view port). Assuming that the request latency is low, the box will be fully loaded when user scrolls to it. I found combining both the shimmer UI approach and this usually makes the injection of dynamic content less disruptive to user flow.
- wruza 5y agoOr just leave it empty and never change its size. It may look strange, but our fear of technically correct “nothing wrong” ways is irrational. Many useful services are so much more broken than that, but still are used because of the value they provide. And we tend to ignore this in real world, so it’s really just the designer’s OCD. When an information/ads stand is half-empty, when roads are padded with safety zones, when spatial configuration of anything real is technical, then nobody notices. But when the same happens on a site, every figma guy goes mad about the extra space it takes.