compose-samples VS material-components-android

The official documentation provides a comprehensive guide on the basics of Jetpack Compose, components, layouts, theming, and more advanced topics.

Apparently Jetpack Compose is an Android copy of SwiftUI?

https://developer.android.com/jetpack/compose

Only two HN threads with comments: https://hn.algolia.com/?q=jetpack+compose

If you want to take a look at code, we have the Jetnews sample app that support different screen sizes. And Jetcaster also implements features such as table top mode.

check this out : https://github.com/android/compose-samples/tree/main/Crane

So I would say that instead if learning everything from Android SDK, you should just set a goal to create some app. Learn about Activities, their lifecycle, layouts (or Compose if you want to be more up to date). Try to implement your app based on this. Then improve your app using Fragments and their lifecycle. If you truly want to understand Views, which are essentially the building blocks of Android UI then I would recommend implementing your own custom View, which will have completely custom look - it is cool thing to try and you will learn how it all works inside.

The compose samples by Google are a good reference to look into: https://github.com/android/compose-samples

Basic understanding of Jetpack Compose.

The compose-samples repo has a comprehensive list of samples ranging from low to complex projects which might be worth a look.

For instance, there is a link to this repository, that contains all sorts of samples, that are up to date and ready to use. That's cutting edge, which is a recommended start.

It works with both. Components for the view system are available on Github.

By going to the Github doc of the material components lib, you can change branches and easily check when the design was updated. The latest release with the old design is 1.4 (see this doc).

TargetSDK is 33

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

You mean this one? https://github.com/material-components/material-components-android/blob/master/docs/components/Search.md

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

It's probably worth filing an issue about it https://github.com/material-components/material-components-android/issues