Android 14 will soon restrict users from installing apps that work towards outdated versions of Android. This new implementation will become effective beginning in January of this year.
Times are changing, and so are mobile operating systems – in particular, Android known primarily for its “openness” and user-friendly flexibility will introduce some new developments with regard to the next major Android OS upgrade, namely Android 14. As such, Google has recently announced some new guidelines for developers that are intended to reduce the occurrence of malware and security compromises for end users.
More specifically, it looks like Android 14 will soon restrict users from installing apps that work towards outdated versions of Android. This new implementation will become effective beginning in January of this year.
While the Play Store has generally required Android app developers to maintain their apps to be compatible with updated security features and such, a new set of guidelines have been pushed which now require new apps to target Android 12. Meanwhile, Wear OS apps are required to target Android 11 or higher. Google did explain the reason for this new change:
“Every new Android version introduces changes that bring security and performance improvements and enhance the Android user experience. Some of these changes only apply to apps that explicitly declare support through their targetSdkVersion manifest attribute (also known as the target API level). Configuring your app to target a recent API level ensures that users can benefit from these improvements, while your app can still run on older Android versions. Targeting a recent API level also allows your app to take advantage of the platform’s latest features to delight your users. Furthermore, as of Android 10 (API level 29), users see a warning when they start an app for the first time if the app targets Android 5.1 (API level 22) or lower.”
This new and stricter implementation will essentially block the installation of outdated apps, which would include apps obtained via sideloading .apk files, as well as app installations made through third-party app stores. This comes as a rather interesting change, given that Android is primarily known for being easily open to modification and tweaking.
There are some exceptions, however – Google states that “Permanently private apps” which are restricted to usage for specific organisations via internal distribution aren’t required to meet the target API level requirements. Essentially, apps not intended for commercial distribution – such as enterprise-essential software applications – are exempt from the guidelines.
With that said, whether or not this new implementation proves to be effective in preventing unwanted malware and security issues remains to be seen, although on the other hand it brings us one step closer to Android 14’s arrival this year.
In other Google news, the company has finally completed its shutdown of Google Stadia, a cloud gaming platform launched back in 2019. Google issued refunds for digital purchases made by users, and even provided a tutorial on how to use the Stadia controller with bluetooth-compatible devices. The company stated a lack of traction as being one of the main causes for the service’s closure.
1 Comment
This is a great blog post! I have been following your blog for a while now and I really appreciate the work you put into it. Keep up the good work!