X

Third-party Android launcher developers band together against Google

Developers of a few popular third-party Android launchers have come together. They are urging Google to ensure gesture navigation, app switcher, and other aspects work reliably on custom launchers.

Google continues to ignore custom launcher developers

Custom launchers continue to remain a big part of the Android ecosystem. They offer much more flexibility than the default Android launcher many smartphones ship with.

However, Google has dented the appeal of third-party launchers primarily because installing them breaks some key functions and features. Google introduced gesture navigation in Android 10, but this critical aspect of the Android User Interface (UI) doesn’t work properly in third-party launchers.

Custom launchers routinely fall back on the archaic three-button navigation as key aspects of gesture navigation falter, stutter, or even hang randomly. This is because the default system launcher insists on managing app opening/closing animations and the “Recents” screen. Google does not grant third-party launchers access to the QuickStep APIs for customizing the Recents app screens.

Since 2010, custom launcher developers and users have complained on public forums and social media platforms. Needless to say, Google and other Android manufacturers seem to ignore these concerns.

Interestingly, Samsung, Motorola, OnePlus, and Nothing have resorted to creating their custom UI skin, launchers, and workarounds for these issues. However, none of these manufacturers seem to be compelling Google to mend its ways.

Third-party Android launchers teaming up to force Google?

To draw Google’s attention, the developers behind some popular custom launchers, have teamed up. The makers of Smart Launcher, Niagara, Nova Launcher, and Lawnchair are reportedly conducting a survey.

These developers are asking for public feedback about the problems that users face with custom launchers. It appears developers are hoping the collective voice of a large group of custom launcher users would force Google to listen and take remedial action.

Google can fix most of the issues third-party Android launchers face. The search giant has to simply grant them access to the QuickStep APIs.