IssueTracker

Material 3 comes with some new principles. One of them is Design Tokens. According to the short description on the Material website:

Tokens store style values, such as colors and fonts, allowing style values to be applied consistently across designs, code, tools, and platforms.

This fits what all files in this package are. Unfortunately, the Material3 library marks them as being internal, which unnecessarily complicates the work for developers using Material You.

While some of the tokens in the package linked above are dedicated to some specific components such as OutlinedCardTokens, some other Design Tokens are important and should not be marked as internal. This includes but is not limited to: ColorSchemeKeyTokens, ElevationTokens, TypographyKeyTokens, etc. And of course, this also includes functions that use these tokens such as the ColorSchemeKeyTokens.toColor() extension function.

These Design Tokens are important for developers applying custom styles to some components. Changing the typography of a Text component already means "applying a custom style." If I, as a developer, want to create a CustomComponent by following the Material You guidelines, I would create a CustomComponentTokens object, and I would add the default values of my CustomComponent in there. Unfortunately, MaterialTheme.colorScheme.background can only be called from a @Composable function. There are a couple of other alternatives; some developers would add the default values directly in the parameter of the Composable function, and some other developers would duplicate the ColorSchemeKeyTokens object and ColorSchemeKeyTokens.toColor() function.

The point is, defining everything as internal is a bad practice. It favors inconsistencies between different projects based on Material 3 and with the Material3 library itself. Please consider avoiding this internal trend, there's still time for Material3.