Android 13 will make it easier for more phones and ROMs to support Material You

The dynamic Material You platform for Android is nice, but it hasn’t been adopted by many apps yet, especially when it comes to the big names. Partly because it’s a messy process right now, and the Google Apps side libraries for material implementation, you’re forcing a allow list that limits compatibility with some certified manufacturers. Fortunately, Google tells us that this will change in Android 13. According to a reliable source, Google has also dropped its requirement that smartphone manufacturers implement Material You on Android 12.

Those who didn’t live under a rock last year probably know them Google articles for you topics, which allows choosing colors from background and analyzing them into a custom dynamic theme with unique accent colors and colorful background colors. It’s all automatic and keeps contrast to a minimum for accessibility while providing a look that many find beautiful.


This feature first appeared with Pixels running Android 12 but became available in other manufacturers’ Android source code for use with Android 12L/12.1. Google has even created a series of patches that will allow smartphone makers to bring the feature to previous Android 12 versions if they don’t want to put in any more effort than is absolutely required.

Custom custom themes, courtesy of Material You.

In February, a reliable source provided us with documents that showed this Google would request material that you support for its content management system (Google Mobile Services) License. Basically, if you want your phone to run Android 12 and have access to the Google Play Store and other apps, you’ll need the Material You app. This might make sense, except that we recently found out that Google was also forcing a allow list of libraries that it provides to app makers for the Material You app. This means that developers who use Google’s libraries in their apps to create Material You apps will only see them work on phones that Google has expressly approved for the Materials you’re working on. Mix up the requirements of GMS, and things are starting to look incredibly restrictive, with Google Both Enforce “You Material” as a condition but then only allow certain companies to actually use it. It is a confusing and frustrating situation that relies on understandable limitations.

It’s not intuitive, but Google’s interpretation of it is Why There was a checklist to start with that makes sense. There are two main things to remember. First, materials created to ensure that personalization does not interfere with accessibility. The Google He invented his color space just for you material, all to make sure it has a perceptually accurate way to measure brightness and contrast. This is to ensure that the colors generated by the system do not conflict in a way that makes buttons or text difficult to read. The company worked, and this system works very well, but that brings me to my second point: There is nothing stopping smartphone manufacturers from making bad and stupid changes to Android. In fact, they like to do it under the guise of product difference, deluding themselves into believing that their weird theme, arbitrary changes to the user interface, and confusing reorganization are somehow an added value to their product, rather than just wasting time and effort delaying updates and breaking expected behaviors.

All this means is that there is nothing stopping smartphone companies from implementing Material You but then changing it in a short-sighted way that breaks the way it is supposed to work in a way that interferes with accessibility. Frankly, they would almost certainly do something like this if they were given freedom, simply out of ignorance. The only way Google can verify that they’re doing it “correctly” is to test each app, and that’s how you end up with our allow list.

Fortunately, that mess will be cleared up eventually, starting with this GMS license change. We’re not sure exactly when it will change, but a reliable source tells us that Google has dropped its Material You requirements for Android 12 GMS licensing, and only enforces a specific set of standards on devices that actually implement them. Moreover, Google is planning to get rid of the material list allowed entirely by the material library with Android 13, according to comments Regarding Issues on the project github. Google further tells us that it plans to create a series of automated tests that verify that the material executed correctly, but not until Android 13. According to a Google spokesperson:

“In Android 12, there is no automated testing to check if vendors provide color requirements that meet visibility, readability, and accessibility requirements. To enable vendors to participate in the material you use from day one, we work with vendors individually to implement and verify the material you use from them, and then enable Material You for them using this allow menu. Vendors can access Android Partner Engineering to begin this process. This ensures that vendors do not accidentally create colors that affect readability, and that developers and users can expect a consistent experience with the material you are. Android 13, automated testing of color schemes will allow for a different strategy.”

In the meantime, small smartphone manufacturers can apply to be included in the allow list, and Google has made it seem like a simple enough process. But there is an unexpected end result.

The current allowlist status means that the custom ROM cannot perform Material You on Android 12 if the device manufacturer they are developing the software for has not been approved by the manufacturer. This sounds like a “whatever” issue, but it has other repercussions. In many cases, ROM maintainers are also app makers, so this has the indirect effect of discouraging some of the most influential Android community developers from creating Material You compatible apps at the moment. Google indirectly encourages some of its biggest and most influential fans Not To approve an item you are. We reached out to Google to see if there’s anything ROM developers can do to get around this issue before Android 13 “fixes” it.

You may be pretty, but the developers haven’t embraced the dynamic color themes as quickly as we’d hoped. There are some Updated applications to use Ant material attributesbut I hope that these upcoming changes will make life easier for developers and encourage further adoption.