Have a question about theming. For things like typography, the values seem to be relatively static. However, if you look at material theme colors, those fields are specifically declared as mutable state and the constructor parameters are not properties, but simply values that are used for creating the mutable state instances. Why is this?

I think it’s for animation, and colors are more likely to be animated between than typography.

It just creates a ton of boilerplate, since you have to: • declare the constructor argument • declare the mutable state field • declare the argument to the copy function • declare the argument to the updateFrom function • declare the argument in the creation fuctions (ie. lightColors(), etc..)

Not sure what you mean – you don’t need to do all that to use MaterialTheme

Could you expand on the boilerplate? This is only needed if you are building your own custom themeable colors object, and you care about optimizing for usecases when it is being animated. If you know that your colors will never change / animate, you can just define it as a normal data class / similar.

Thanks @Louis Pullen-Freilich [G]. I was wondering what the use case was for not making it a data class. I was simply duplicating what i saw in the MaterialDesign Colors class. Unfortunately our UX has their own design system they are working on which doesn’t match up with MaterialDesign.