I haven't used your latest "native widgets" (GTK) build, but as long as the UI isn't programmed to be as async as possible, then any non-UI related event will slowdown or micro-block the UI, causing the noticed latency.

That's interesting.�� ��Yes, we need async updating without the microblocking dragging down the speed.�� Is the GTK build ready for testing now?

I know I'm speaking the obvious to you here, but if you look at things like Android Architecture there is a lot to learn from, because mobile users expect significantly faster, non-blocking UIs that desktop, and not to mention web (although this is is changing too).

It's a good point.

Shaping