Not sure where else to put this so I'll put it here.
Kotlin's Flows are pretty neat, they're basically async generators aka Rust's async streams aka reactive streams, well integrated with Compose
Model-View-Intent is a pretty interesting design pattern that seems like it fits well with Compose's unidirectional data flow principle. The basic gist is that the entire UI state is one stream from the model to the View (each update essentially provides the View with a new copy of the state), while user actions (Intents) go the other way as one stream. Honestly pretty difficult to describe but I think some of the concepts are applicable. It's kind of a "restricted" version of MVVM.
We need to decide how we want to structure the internals, and where we want to take the project as a whole.