# compose

Travis Griggs

07/08/2022, 11:50 PM
As I try to learn Compose, I find myself really struggling with what is Good(tm) in a compose universe, what is unacceptable, and what is just distasteful. Most of my Android experience is a couple years back, and I'm currently trying to port some BLE scanning code that has lots of references to Activities, and Intents, and RecyclerViews, but no ViewModels. So I end up having to ask myself "is there a better/newer way to do this, or is this a hold your nose moment." I am curious if anyone has any decent up to date good book recommendations? I've done a few of the official sanctioned tutorials, but I feel I'm still missing a lot of how to weave Composable functions (I get that part pretty clear) with the more stateful rest of an Android app.

Sean Proctor

07/09/2022, 12:17 AM
The Android team made a really nice set of guides a little while back. There's some videos on MAD skills to go along with them. It's probably also worth restructuring the rest of the code as well. There isn't much benefit to move from hiding your non-UI state in views to hiding non-UI state in Composable functions.