A modern programming language that makes developers happier.

kotlinlang

Gotcha, will do some of my own experimenting then. Do you know if theres a way to handle the input on a individual composable level rather than at the top level inside `runMosaicBlocking` but outside `setContent` ? My goal is to have multiple different “screen” analogs each self contained in a single Composable and handling the user input differently and independently. Using LaunchedEffect didnt do the trick im guessing for the same reason as the linked bug report. WOuld i just have to pull that out of the composable level entirely?

I got this mostly working, Im using LaunchedEffect despite [this](<https://github.com/JakeWharton/mosaic#why-doesnt-work-take-place-in-a-launchedeffect>) posted issue and it seems to be working fine but YMMV, this is just a testing CLI so its good enough for me.

<https://github.com/mrf7/KMMtg/pull/24/files#diff-55fcec4f85105db82e8a5f7b41a0789b367250d2a630af78dc96824a692f8cfe> First pass at this, could definitely use improvement and i dont know enough about the compose internals to understand the impact of the issue above