Brief content
-
Android pulls the side load: Developer Verifier checks the applications; Unusual installations require the Internet.
-
Warning of the judge judge judging side attitudes; Play Protect Backports rules for old Android.
-
Accounts of students/lovers are lower fees, but installing the cover of the cover; Adopting or fraud leads to blocks of accounts.
Bad news. Android, which has been quite democratic for years, when it comes to side loading, he locks a lot of things starting next year. Currently, the company spoke in detail about how it will work, and although there are several silver invoices, it can still be gloomy for some of you.
Now Google calculates in detail how the side load will work, starting from the second quarterly release of Android 16. The company insists that “the side load is fundamental for Android” to stay, and for this these new measures are designed to make the side loading more safe to use. But this can still lead to problems.
When the user tries to install the application for the first time, a new system service called Android will be activated, called Android. This service will communicate with Google's bacand to confirm that the application key and the package name were presented by a proven developer. The developer Verifier will support the cache of the settings of popular, already verified applications, allowing them to install them without a network connection, so it should not check the online one when you want to install the application. However, for less common applications, not in the cache you will need to connect to the Internet, which can suck for some.
The new system recognizes the legal need for some users to install applications from independent developers or third -party stores, and tries to go around them. In order to simplify the process for third -party applications stores, Google also introduces the “preliminary token”, the cryptographic drop that is stored can transfer the system to check the application without additional network calls. These changes will also be returned to the old versions of Android using updates to Google Play Protect.
Google also described in detail his plans for a separate type of account for students and amateurs. These accounts will have fewer obstacles to check and abandon the standard registration fee of $ 25. Nevertheless, they are delivered with a significant restriction designed to prevent abuse of intruding actors: strict restriction on the number of devices that can set their applications. To ensure compliance with this, the user must provide a unique identifier to the developer, which then must manually resolve this specific device in the Android developer console, effectively limiting the distribution of a small, known group of people.
The company also outlined its strategy to prevent bypassing bad entities. The developers will have to prove the ownership of the application package, demonstrating that they have the right signature key. Those who are caught in the distribution of harmful programs will face restrictions at the account level, blocking all applications related to their installation. Google also claims to have its own methods for detecting fraud with identification during the verification process, including the definition of false representations generated AI.
All this may seem insufficient when it comes to third-party stores, such as F-Droid, which make the point of view to make applications from independent developers who do not rely on accessible Google servers. But we will have to see how all this turns out, and whether Google can reach a point when everyone is happy.
Source: Android Authority
