Silly question but..... for `State` updates to work properly, do they have to be directly in a `@Co...

# compose

[Dominaezzz]

Silly question but..... for State updates to work properly, do they have to be directly in a @Composable method? Would it still work with a non-@Composable wrapper method?

[Zach Klippenstein (he/him) [MOD]]

You don’t need to use Composables at all with `State`/`MutableState`. It’s very common for regular classes to define MutableState properties.

[Zach Klippenstein (he/him) [MOD]]

You don’t even need composables to observe changes, see snapshotFlow

[Zach Klippenstein (he/him) [MOD]]

However, if you’re using the snapshotting infrastructure without the rest of Compose, you’ll have to apply the global snapshot yourself somehow, or use more granular snapshots.

[Dominaezzz]

That seems quite magical. My use case is to hide State and expose plain getters in a model.

[Zach Klippenstein (he/him) [MOD]]

Using the low-level snapshot APIs is kind of tricky. Compose will apply the global snapshot once per frame for you automatically, which is where the “magic” comes from.

[Dominaezzz]

Oh, it's global. I see.

[Zach Klippenstein (he/him) [MOD]]

It’s really common to see stuff like:

var yourState: String by mutableStateOf("hello")
  private set

[Dominaezzz]

Thanks for explaining!

[Zach Klippenstein (he/him) [MOD]]

Anyway, if you’re using this with other Compose UI, you don’t need to even know about the global snapshot or snapshotFlow.