What it’s worthwhile to know
- Google says Chrome on Android now experiences 48% fewer scroll stutters than in 2023.
- The enhancements are the results of almost three years of engineering work.
- Google redesigned a number of elements of Chrome’s rendering pipeline to attain this.
For those who’ve felt recently that the Chrome app on Android is smoother whereas scrolling by articles (like this one, even), it is most likely since you’re utilizing the top results of three years of engineering work behind the scenes at Google.
Whereas Google could also be focusing closely on new AI options, like bringing extra Gemini into Chrome, there are additionally loads of different enhancements the corporate has been quietly engaged on for Chrome on Android. Take, for instance, that split-second stutter you generally discover when scrolling by a webpage earlier than it carries on as regular, which Google internally calls “scroll jank.”
In a brand new engineering weblog put up, Google says Chrome on Android now experiences 48% fewer janky scrolls than it did again in late 2023.
Based on Google, scroll jank occurs when Chrome fails to replace the web page shortly sufficient to maintain up along with your finger. Though the delay might solely final a fraction of a second, it is nonetheless sufficient for the human eye to note, making the entire scrolling expertise really feel jerky.
The corporate says that eliminating these interruptions wasn’t so simple as making Chrome quicker. Google explains that Chrome’s rendering pipeline is way extra complicated than a typical Android app as a result of the browser spreads work throughout a number of processes for safety and stability. Which means there are much more alternatives for tiny delays to construct up earlier than a body lastly seems on display.
To sort out the issue, Google first spent months instrumenting Chrome’s rendering pipeline to establish precisely the place scroll stutters had been occurring.
It then launched a collection of architectural enhancements over the next years, together with rerouting contact enter by a quicker path, lowering communication delays between browser processes, and transferring extra work onto the GPU.
Google additionally labored alongside Android itself to prioritize the working system’s enter threads, serving to contact occasions attain Chrome extra constantly, thus serving to it produce frames extra reliably.
Google went into much more depth about precisely the way it mounted all this, however I will not bore you with the technical particulars. In case you have been questioning why Chrome does not really feel so dangerous on Android anymore, because of this your feed may really feel rather less jumpy than it did a few years in the past.
