![]() We don't know if Google has communicated this change to OEMs, but we hope that more OEMs take notice of this change and decide to incorporate the API in their forks of Launcher3 to improve the experience of using third-party launchers. Rotten Tomatoes, home of the Tomatometer, is the most trusted measurement of quality for Movies & TV. In fact, one OEM we talked to, ASUS, told us that they plan to bring this API in their Android 12 update. Unless an OEM goes out of its way to revert the commit, break the code, or refuse to update Launcher3, then we should see this API get added to OEM launchers whenever they rebase on top of the upcoming Android 12 release. Given how tightly Google controls full-screen gesture navigation, we suspect that most OEMs don't heavily modify code related to gestures and/or QuickStep. So what will it take for this API to be added to other Android devices? Unfortunately, there's no easy answer to that, because we don't know exactly how each OEM develops its launcher app. As a reminder, Pixel Launcher is built on top of Launcher3 just like most stock launchers are, but it also includes some Pixel-exclusive features.) (Pixel 2 owners can sideload a newer version of the Pixel Launcher which has the API from a more recent Pixel device, but user reports indicate the animation is still buggy even if it works once in a while. And despite the Pixel 2 getting its final update in December, that update didn't include the Android R QPR1 codebase, which is why Pixel 2 owners running Nova Launcher v7 don't have the same experience as other Pixels. It's also worth noting that this API is only accessible on Google Pixel phones after the December Pixel Feature Drop, which coincides with the public Android R QPR1 release. Unless you use a Google Pixel phone, that is. The result, as most of you have probably experienced, can be a bit janky, with transitions that don't look fluid and seamless. ![]() This can be overridden with root access if the third-party launcher supports it, but for most users, this means that a third-party launcher app will always rely on the stock launcher to handle gestures and the recent apps screen. ![]() Thus, the QuickStep component was born, and because of its privileged nature, Android only allows the preinstalled launcher app to be set as the recent apps provider. ![]() To do both of these, Google decided to move the code that handles the recent apps screen from Android's SystemUI to Launcher3, Android's open-source launcher app that most OEM stock launchers are forked from. They also wanted to let users access their entire app list from the recent apps screen. In order to make gestures feel as fluid as possible, Google needed to make app transitions look seamless. Google first introduced gesture navigation in Android 9 Pie. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |