As expected, the development of Android 14 going from strength to strength, so Google has published the first beta of what will be the next stable version of its mobile operating system, which has long since diversified into other horizons such as vehicles and televisions. It is important to note that this release is focused on developers and people who voluntarily want to test it in order to report bugs, although that does not prevent curious people from using it to simply see what it brings and how development is going.
Google wants Android 14 to improve things like support for tablets with large screens, support for foldable devices, security, performance, and privacy. Following what is stated in the official Android developer blog, we first find ourselves with a “smarter system user interface”, which is composed of a framework (framework) that provides the services and a system user interface (System UI) that provides control over those services.
Going deeper into the news at the interface level, we find a more prominent back arrow to facilitate the understanding of the feature itself and the interaction with the application, which also complements the wallpaper or theme of the user’s device. On the other hand, apps can add custom functions to the share sheets they invoke, and the system now uses more app signals to determine the ranking of direct action targets.
Android 14 improves per-app language preferences to enable dynamic customization via the corresponding section in System Settings, as well as giving IMEs a way to learn the current app’s user interface language.
Google’s upcoming mobile operating system, still in development, has introduced the attribute accessibilityDataSensitive to allow apps to limit the visibility of specific views to only those accessibility services that claim to help disabled users. In this way, the door is opened to protect user data and avoid critical actions that can be executed unintentionally.
With the publication of the first beta of Android 14, Google has invited developers to test their applications on the system using some device (on paper that can be sacrificed and is compatible, with special mention to the Pixel) or resorting to an emulator that runs the system. The Mountain View giant has asked developers to review the behavior of the applications, to fix the problems that arise and to direct the compilations towards Android 14 by testing the compatibility changes in the options for developers.
Moving away from the parts closest to the end user, there is the API Path, which provides a flexible mechanism for creating and rendering vector graphics. Said API, which was already present in the system, has been updated to include the functionality to interpolate between routes whose structures exactly match, which allows transformation effects.
As we can see, the first beta of Android 14 has arrived with some logical developments and new features. In addition to what was mentioned in the Android developer blog, the future version of the operating system will also highlight, or at least that seemed to be the intention in the past, for improve support for third-party stores, an aspect that to a large extent comes from the pressure in favor of the opening of the platforms that has been seen in recent times and the one that the governments of the United States and the European Union have joined. At this point, it doesn’t hurt to remember the possible release of the web rendering engine and the probable support for third-party stores on iOS.
Who will try the news of the future Android 14? If so, do not hesitate to take a look at our installation tutorial, where we indicate the compatible devices and expose the possibility of using Android Studio to put the emulator up and running. (https://www.stocktargetadvisor.com/)
