If something saved Google from regulators’ control and claims to a potential monopoly, then unlike Apple with iOS always allow third-party transactions, in-app payment systems, and in-app loading. Not for nothing has Europe made progress in regulating so that operating systems, read iOS and derivatives, must acknowledge these measures, which Apple has always rejected, with arguments that suggest harm to the security and privacy of users.

However, and as we have read in some media today, Google appears to be reviewing its policies in this regard, and that his goal would be to move closer to the Apple model. This approach is quite understandable, given the vicissitudes faced by Christian Ghisler, a veteran developer and the very popular Total Commander. Software that some of us started using on computers in the 1990s, which some time ago made the leap on Android and became one of the most popular applications in its category.

One of the functions of Total Commander is that until now, and by allowing you to explore the file structure, it also allowed you to install applications. This feature is common in this type of application, which in turn is one of the reasons for its great popularity. However, a few weeks ago, Ghisler received a message from Google indicating this If the app is not modified, it will be removed from the Google Play Store within a week in accordance with Android application store policies.

The links in the message the developer received pointed to the following points:

«An application distributed through Google Play cannot be modified, replaced or updated in any way other than the Google Play update mechanism. Also, the application may not download executable code (such as dex, JAR, .so files) from a source other than Google Play. This restriction does not apply to code running on a virtual machine or interpreter where it either provides indirect access to the Android API (such as JavaScript in a web view or browser).

Third-party applications or code (such as SDKs) with interpreted languages ​​(JavaScript, Python, Lua, etc.) loaded at runtime (such as not bundled with the application) must not allow potential policy violations from Google Play.»

From the Total Commander installation feature can be used to update, the developer updated it so that it would no longer be possible, believing that this would resolve the issue. Another response he received from Google was as follows:

«As mentioned above, their apps (APK versions 1031, 1032, 1033, 1034, 1035 and 1036) cause users to download or install apps from unknown sources outside of Google Play.»

That’s pretty ambiguous, really. What does it mean “causes users to download or install applications«? The fact that the selected word was not “allows” means that Google’s response is not as clear as might be expected. In any case, the developer excluded the possibility of installing applications from Total Commander, and with this version he was able to renew Google’s approval.

This step search engine companies put the rest of the developers of this type of application in a tense situationbecause they hope that what happened to Total Commander also applies to their applications. And the fact that the only solution Google adopted was to remove the installation feature leads us to interpret the ambiguity of the report theories that “causes” in this particular case is synonymous with “allows.”

So is Google following iOS in the footsteps of Apple? Android’s security policies for installing applications, which are much more tolerant than Apple’s policies, are known to have caused more malware on this platform. Restrictive measures of this type could lead to greater safety for users. But at what price?

First, such a measure would not be very welcome for most Android users, advocates of the open model of the Google operating system versus Apple. I am sure that the search engine company is well aware of this and the potential negative consequences it would have to face if it adopted this new policy.

But it’s not just that. As I mentioned at the beginning, Apple is facing regulators around the world precisely because of its policy in this regard. We can expect in the short term the law stipulates the obligation to allow such a function. And as far as we know, we can imagine that Google’s legal department is even more aware of this. And what exactly should be the point of adopting policies at this point that are against the regulatory future in this regard?

Personally, It’s hard to believe that Google is going in that direction, although it is true that what happened to Total Commander clearly shows in this line. What do you think? Do you think Google has changed its mind and is moving towards a model closer to Apple, with restrictions on sideloading?

With information from Android Police