TimeRangePicker VS material-components-android

2. TimeRangePicker

TargetSDK is 33

[Tokens/Color] Added U color resources for contrast mode support.

I'm not a dev, but I'm curious about this, cause I thought Material Components was made years ago as a library for devs to dynamically use said material components, so they would have an easier time updating their apps when the guidelines changed. Did I interpret it wrong?

Material Components has ToggleButton which does exactly what you want

UI: Material components

Android Architecture Components, especially: Stateflow, Flow, ViewModel , Room, Jetpack Navigation, DataStore, and Material Components for Android

The "old" way: You'll likely use components provided by the MDC-Android library, with some tutorials here. You arrange components using things like FrameLayout, LinearLayout, ConstraintLayout, and ScrollView. Use TextView for text, ImageView for images, CardView for cards, and so on. You do set values for padding/margin/text size/color/etc, or they can be provide by themes/styles (similar to CSS, kinda). Android has its own units for dimensions. You will often jump between code and XML.

As others replied, pretty much nothing has been released yet, but it's most likely a matter of weeks now. You can see here the different colours used by the future M3 components, and searching for the names in this repo, how they are used.

I've been following the development for quite a while now. It's really interesting, but I feel like theming an app using Material You was made overly complicated. For example, typography guidelines (here) were changed, the previous guidelines were easy to understand, but it's not as easy anymore. Same thing happened with colors and theming overall. Material You is quite interesting, but overly complicating its implementation won't make it appealing to developers.