It just occured to me that

MutableStateFlow

can be used for databinding. Did anyone try that yet?

Do you mean it’s automatically unwrapped just like

LiveData

?

I meant

MutableStateFlow

(edited). @wasyl I mean you can hand it to UI code, and it will get the current value, the updates, and be able to push a new value.

Yup, we used it in one of our projects

When I say databinding, I'm not referring to any framework. It works on Android indeed, but could also work on Kotlin/JS, and on Kotlin/Native single-thread.

Then, yes! 🙂

KVision allows using

StateFlow

for databinding with observable components. But I haven't used this functionality in any real project yet.

@louiscad That sounds interesting, do you have some sort of a gist? or repo that I can check out? I'd really like to see how you guys implemented that

@andylamax I have no gist at the moment, but the idea is to basically pass a

MutableStateFlow

to the part of the code that will manage the UI, or a part of it. I pass it as part of a cancellable suspending function (for when that UI part needs to be disabled), and in that function, I collect the

StateFlow

with

collectLatest

or alike, update the UI, and wait for user interaction to input a new value that is then put into the same

MutableStateFlow

.

We're using it to emit (non-jetpack) view models from our state management library, Workflow