3 ms·
I don't know that I will ever be happy with lazy loaded UIs over a more traditional "Deliver everything first, update later" approach. There's a nice middle gr
by onion2k 7y ago
I don't know that I will ever be happy with lazy loaded UIs over a more traditional "Deliver everything first, update later" approach.
There's a nice middle ground.
In the app I work on very little is included at start up. It's literally just the components for the first screen you see. Then it pre-loads more components whenever the browser is idle based on what the user is likely to need. If the user does something that needs a component that isn't available yet it lazy loads it as usual.
If you only use lazy loading the user has to do something that needs a component and then wait until it's available. The strategy I use means there's an additional phase that utilises the time when the browser is idle, so it's much more likely everything is available before it's needed. It works well.