Material You should finally catch on with Android 13

One of the most characteristic aesthetic innovations of Android 12 was the introduction of Material You, the style of automatic customization of the system tone thanks to dynamic themes based on the background.

Google has adapted most of its apps over time (Google News the latest) and since many developers have not yet adequate has even thought of imposing its use, as well as releasing it in the AOSP (Android Open Source Project) for easier integration by the various OEMs. The problem is that in Android 12 the process of implementing the new system in apps is quite complicated and restrictive, but this could finally change with Android 13.

But what are the problems of introducing Material Youand how they will be resolved with Android 13?

Android 12 and Material You

Before understanding why Google he thought of certain rules, we have to take a step back, and understand how it works Material You. The new interface was created so that the customization did not interfere with the functionalitymeasuring brightness and contrast accurately (starting from the background on the device) in order to return an interface pleasant but without rendering difficult to read texts and buttons.

But what if a OEM takes it easy? It is possible that it spoils everything, precisely by interfering with accessibility. The only way Google can verify that everything is working, is test each implementationand that’s how he introduced the OEM list who can use Material You.

Obviously gods were born from this problemsbecause on the one hand there are OEMs (few) who can use Material Youand even Google has enforced support for licensing GMS (Google Mobile Services), necessary in order to use the services of the Play Store. On the other hand there are the app developersto which this list of libraries has been released to implement Material You, which causes apps that use Google Material You libraries to only work on phones approved by Google for the interface. Practically Google imposes a requirementbut allows you to use it only to some companies (and up to a certain point with good reason).

Android 13: change everything

Now this problem will finally come Resolved. First of all, Google has already introduced a change to the GMS licenseabandoning the Material You requirement for the GMS license of Android 12 and only imposing a specific set of standards for devices that actually implement it.

But the most important news will come with Android 13as Google plans to eliminate his list of libraries Material You just with the new operating system. For that time, there will be a number of automated tests that verify that Material You is implemented correctly.

All right then, the OEM minors may be included in the library listand Google has implemented a pretty simple process for doing this, but there is obviously a problemwhich concerns the Custom ROM. These in fact Not will be able to use Material You whether the manufacturer of the device they are developing the software for has not been approved, and even if it seems like a minor issue, it matters ramifications. One above all, lies in the fact that many developers who keep Custom ROMs are also among the most influential app developers of the Android landscape, and they won’t be particularly inclined to make them compatible with Material You if they can’t work on the devices they maintain.

Obviously with Android 13 the problem will not occur again but for the moment this clashes with interests from Google, which is pushing developers to make compatible their apps with Material You. It is still unknown if there is a way to get around the lock in Android 12, but surely the changes in Android 13 will make life easier for developers (and spread Material You, finally).