@chi we delay the initial display for simplicity. Most cases for us the evaluation takes <1s but we have got some animations that hide for 2s then fade in for 1s on the particularly complex displays.
This technique works particularly well for dynamically embedded views (I’m finding embedded views are still a little bit laggy, but I know that various solutions are being discussed by Ignition dev/support). If you have a fade in on the embedded view component and the child views, it hides the initial binding evaluation to get the appropriate view path and then the child view slowly fades in. This gives the effect of a deliberate staggered animation, when in fact it’s just hiding the loading of the views. But I digress…