Displaying components independently is considered bad UX (because of content shifting around, things &quot;appearing&quot;, which sometimes change the layout upon loading / filling a container). The solution most commonly seems to be to load components and their dependencies asynchronously, but render only once the previous component in order is already displaying. 
How does Aurelia behave with this matter? 
See more info about the issue here: 
<a href="https://jakearchibald.com/2016/link-in-body/">https://jakearchibald.com/2016/link-in-body/</a>
And a demo of the issue:
<a href="https://jakearchibald-demos.herokuapp.com/progressive-css/naive.html">https://jakearchibald-demos.herokuapp.com/progressive-css/naive.html</a>

Displaying components independently is considered bad UX (because of content shifting around, things "appearing", which sometimes change the layout upon loading / filling a container). The solution most commonly seems to be to load components and their dependencies asynchronously, but render only once the previous component in order is already displaying. 

How does Aurelia behave with this matter? 

See more info about the issue here: 

https://jakearchibald.com/2016/link-in-body/

And a demo of the issue:

https://jakearchibald-demos.herokuapp.com/progressive-css/naive.html

Does Aurelia display its components in order, or independently, as soon as they are loaded?

Product

Explore

Company

Blogs

Partner with us

Support

Comparisons

Comparisons