I'm reading <https://medium.com/androiddevelopers/effective-state-management-for-textfield-in-compos...

# compose

[Colton Idle]

I'm reading https://medium.com/androiddevelopers/effective-state-management-for-textfield-in-compose-d6e5b070fbe5

which says

Even just using reactive streams to represent your state (e.g. StateFlow) without delays might cause issues as the update event dispatch is not immediate if you’re using the default dispatcher.

Maybe this is more of a corotuines question, but if you're using the default dispatcher (which is main on android?) wouldn't that be immediate?

[jw]

Main always still posts. Main.immediate is the one which does not post if you already are on the main thread

[Colton Idle]

TIL theres Main and Main.immediate

🙈

[Colton Idle]

Also, maybe dumb question but what do you mean by "still posts"? Like goes into a queue?

[Francesc]

the main point behind that post is that you should only update the state for a text field synchronously, you should not update by passing a message to the viewmodel indicating "input updated", which goes to a queue and then is processed, creates a new state object which gets published to the UI, which ends up updating the actual display of the text field. You can still post stuff to the viewmodel, but you should update the field state synchronously to avoid issues

[Francesc]

the way I've solved this is by creating a StateHolder to host the input field state

[efemoney]

Or use mutable state in your view model

[Francesc]

that works if you have a MVVM approach, but if you opt for MVI, where you are posting messages that end up in your reducer, that won't work here

[Landry Norris]

It’s also best to avoid using compose state in your view model if using multiplatform. StateFlow is much easier to use with non-compose UI libraries.

[Colton Idle]

i like compose state because its so much easier to work with than stateFlow

[Colton Idle]

¯\_(ツ)_/¯

[Landry Norris]

Not quite sure why they say to avoid flows, though. I’ve always used a StateFlow with TextFields and haven’t seen any issues. I always make sure that methods immediately update the flow, without any intermediate steps like in their first example.

[Landry Norris]

It seems like the main issue was the async operation between. It seems like it would be easier when working with flows to have your validation step map from the text state flow as an easy way to make sure it doesn’t slow down the text state.

[Colton Idle]

Yeah. I've used stateFlow with textField once and didn't see any issues.

[Colton Idle]

but the async stuff makes complete sense. you want that state to be updated ASAP. It was a great article though. TIL i learned that with text field you end up having 3 pieces of state 🤯

[Francesc]

if you don't update synchronously you may be missing characters and the cursor may jump out of place

[efemoney]

that works if you have a MVVM approach

It works anywhre ie not limited to architecture 🤔. We use an mvi variant / udf …

[Francesc]

we are getting into the weeds here which is not what the discussion is about, but if you are mutating the state, that's not how I understand and use MVI - in MVI you create a new state based on existing state, and there is a pipeline for the intents to travel to before they are reduced, which is not synchronous.