i keep seeing animation budgets treated like a visual taste issue when a lot of it is really timing and compositing work. a tiny motion can be cheap, and then one extra layer or blur suddenly turns into jank on older hardware.
what’s interesting to me is that teams seem fine with a slightly plainer UI, but they hate admitting one polished transition is the thing making the whole screen feel sluggish. where do people draw that line in practice?
That “one extra layer or blur” line is the part that gets me, because blur/backdrop-filter is where you quietly start paying every frame on a bunch of GPUs, not just once during the transition. In practice, the line I’ve seen teams draw is: if it ever blocks input, it’s not “polish” anymore, it’s a bug. So they’ll keep the fancy transition for a modal or a one-off delight moment, but anything that runs during scrolling/dragging or while data is loading gets a hard budget and a kill switch (reduce motion, low-power mode, whatever). People forgive plain. They don’t forgive “why did my tap not register. ”
that 24px blur over a scrolling list is exactly where the wheels come off.
in practice i’ve seen the line get drawn at “does this make taps feel late?” not “does this look a bit less fancy.” once a transition starts affecting input latency or scroll smoothness, it gets cut fast. people will tolerate a slightly plain screen. they get weirdly angry when the UI feels sticky.
the annoying bit is that teams often notice the blur first because it’s visible, but the real problem is usually compositing cost on the worst device in the room. i’ve had a couple of projects where the fix was just dropping the heavy effect while the surface is moving, then bringing it back when things settle. ugly? a bit. better than a janky app? absolutely.
:: Copyright KIRUPA 2024 //--