Smooth scrolling in Chrome for Android has become ever more prominent thanks to some changes and fixes that Google made in an update to the Android app. This isn’t a small collection of changes that Google made recently. Rather, it’s a series of changes that Google has been making to Chrome for Android since 2023, and has continued to improve upon all the way till now in 2026.
Google details these collective changes in a recent blog post from July 23, highlighting how all of these changes over the past few years have helped to reduce what it calls ‘scroll jank’ in Chrome for Android by a total of 48%. If you’re not familiar with the term scroll jank, it’s the stuttering or hitching that can occur when you’re scrolling a webpage. Google says this happens when “a device fails to present a frame containing an updated scroll offset on time.” The video comparison below shows what this looks like exactly.
Input-to-frame delivery is harder to maintain for Chrome than other Android apps
Fixing this issue in Chrome for Android isn’t a quick fix scenario, and that should be evident by the fact that it’s taken Google around three years to make the improvements that got Chrome to where it is now. According to Google, this is in large part because maintaining a consistent input-to-frame delivery is harder in Chrome for Android than it is for other apps.
This can all be explained visually by the input pipeline. In short, traditional Android apps have a significantly smaller input pipeline than the Chrome for Android app. For any app, whether it’s Chrome or not, two main things are needed to make the scroll animation show up on screen for the user. One, the input event, which tells the app where the user’s finger is on screen. This allows it to “calculate the scroll offset.” And two, the Vsync signals, which Google says “act like a metronome for the device.” The Vsync signals tell the app when to produce the next frame.
For traditional apps, the input pipeline has way fewer processes. The input pipeline for Chrome on Android is more complicated because the steps are spread across several different processes in the Chrome app.
The input events go through these different processes at the same time before the frame can be displayed to the user. Google tackled this problem by indentifying the root causes of the scroll jank and then brainstormed projects to address the issues. Once a fix was in place, it went through the whole process over and over until the scroll jank was reduced by 48%.
The post Google’s efforts to reduce scroll jank have improved Chrome a ton appeared first on Android Headlines.
