Edgar Cervantes
In Brief
- Google has significantly reduced janky scrolling in Chrome for Android, lessening issues by 48% from 2023 to 2026.
- Innovations such as “Input Vizard” redirect touch responses directly to the GPU, bypassing the main browser thread.
- Features like “Input Prediction” and “Direct2Thread” ensure a smooth experience, even during OS delays.
Google is continuously refining Chrome for Android, whether by experimenting with new features in the navigation bar or making essential performance upgrades. The company recently revealed that it has managed to significantly reduce the occurrence of jerky scrolling by 48% from 2023 to 2026. This impressive achievement is due to improvements in frame delivery consistency rather than just speed, leading to a much smoother browsing experience.
As explained on the Chrome Developer Blog, Google initiated a rigorous multi-year effort to identify and resolve the causes of the notorious jank and stuttering issues in Chrome on Android devices.
The main problem lies in missed deadlines for frame updates. If Chrome cannot deliver a refreshed scroll frame before the screen’s refresh window (approximately 16.7 milliseconds on a standard 60Hz display), the result is a stale frame, which users perceive as a jerky experience. Chrome’s multi-process architecture makes it more vulnerable to delays compared to typical Android apps, which use a single thread for both touch input and rendering.
To address these jank issues, the Chrome team utilized automated Perfetto tracing tools to pinpoint where the browser was lagging, which informed a series of targeted optimizations.
A major breakthrough is the introduction of “Input Vizard,” a structural change that allows touch input events to be routed directly to the GPU’s compositor thread, effectively bypassing the congested main browser thread.
Additionally, Google has revamped the browser’s UI handling, implementing enhancements that synchronize the address bar and controls with scrolling, thereby relieving pressure on the main thread.
Other optimizations include a new “Input Prediction” feature, which allows Chrome to create synthetic scroll updates based on previously observed data, compensating for any OS lag in delivering touch information.
Moreover, the “Input Framer” feature allows the browser to hold off briefly to wait for delayed input events, while “Direct2Thread” minimizes unnecessary intermediary thread interactions, thus accelerating cross-process communication.
Interestingly, the majority of these improvements stem from optimizing how Chrome receives touch input rather than how it renders the webpage. Ultimately, if the browser lacks timely touch data, it can’t deliver a seamlessly smooth scrolling experience.
We appreciate your engagement with our community. Please familiarize yourself with our comment policy before contributing.
