> A lot of apps that users use to download and sideload apps (browsers, mail clients, messaging apps) have no reason to go and implement the session-based insta

> A lot of apps that users use to download and sideload apps (browsers, mail clients, messaging apps) have no reason to go and implement the session-based installer API As the article notes even if those apps do want to use the session-based installer API for some reason, they can just flag that the APK came from either PACKAGE_SOURCE_LOCAL_FILE or PACKAGE_SOURCE_DOWNLOADED_FILE to trigger the same side-load protection behavior. Which, yeah, I don't see why something like eg Firefox would be interested in bypassing this behavior.