However, the author makes these assertions:

- No partially loaded content. - No relayout while content loads.

Holding those as hard rules leads to delay or rejection. Instead, while I agree it's better to have everything up front, gracefully handling cases when we don't is important, and some degree of responsiveness, even with partially loaded content, often makes for a better experience for the user than a delay.

Just be up front about it and find ways to keep continuity of relationship and smoothness. Diffeomorphic mappings are your friend...

I saw that but couldn’t really connect it to the rest of the article because none of their examples had data loading.

Like the issue with the osx side bar transition is that the order of operations makes no sense.

When expanding, it makes the buttons vanish only to animate their reappearance from nothing once a panel slides over them.

It would make sense in the physical world if the panel occluded the buttons during transition.

During closing, the reverse problem happens. The buttons aren’t occluded but clip through the panel like it became water.

It happens fast but not so fast that you can’t see it, and there is an unnecessary distortion.

In today’s world of AI, good taste is all we human workers have so we should call out cut corners.