Android Sideloading: Advanced Flow Details Emerge

Google recently shed more light on its upcoming "advanced flow" for enabling sideloading from unverified developers on Android devices. This new process, scheduled for rollout later this year, aims to provide users with more control over app installations. Additional clarifications on the process were provided in an FAQ video hosted by Matthew Forsythe, Google’s Chief Product Explainer.

Google’s upcoming "advanced flow" for enabling sideloading from unverified developers is slated for rollout later this year, bringing new details to light from an official FAQ.

Key Clarifications from Google's FAQ

The FAQ video offered crucial insights into how the advanced flow will function for users.

Device Transferability

Once the advanced flow is enabled on a current Android device, it can be seamlessly transferred to a new device during the setup process. This ensures continuity for users upgrading their handsets without needing to re-enable the feature.

ADB Installs

Installs performed via Android Debug Bridge (ADB) operate differently under the new system. ADB installs are notably not subject to the 24-hour waiting period associated with the advanced flow. However, it was confirmed that there is no ADB command available to bypass this waiting period for other sideloading methods.

App Detection

Google has designed the system to maintain user privacy regarding this feature. Applications cannot detect if the advanced flow is enabled, as it is an operating system-level change. This prevents apps from potentially altering their behavior or restricting functionality based on a user's sideloading preference.

Updates for Unverified Apps

For continued use and maintenance of unverified applications, the advanced flow must remain enabled to update them. The limited 7-day bypass window, a separate feature, is explicitly intended for app testing purposes, not for the long-term installation or updating of applications.

Developer Mode Status

A significant concern for many users revolved around developer mode. Google clarified that developer mode does not need to remain active for continued installation of unverified APKs after the advanced flow process is completed. This directly addresses potential conflicts with applications, such as banking apps, that may restrict functionality when developer mode is active.

Developer NDAs

Regarding the verification process, Google assures developers that it does not involve reviewing the application's content. Therefore, the process is designed not to violate developer Non-Disclosure Agreements (NDAs).

Unanswered Questions

Despite the detailed FAQ, certain scenarios remain unaddressed, leaving users and developers with lingering questions about the advanced flow's behavior in specific circumstances:

• Impact of Factory Reset: The video did not clarify the impact of a factory reset on the sideloading enablement. Would the advanced flow need to be re-enabled from scratch after such an event?
• ROM Flashing Durability: There was no information provided on whether sideloading remains enabled after flashing new ROMs, a common practice among advanced Android users who customize their device's operating system.
• Single-Device Transferability: The FAQ did not address the transferability of sideloading enablement without two devices present during the setup process. This might be relevant for users who lose or break their old device before setting up a new one.