# MutableStateFlow for methods (or how to make an observable function)?

**URL:** <https://discuss.kotlinlang.org/t/mutablestateflow-for-methods-or-how-to-make-an-observable-function/25763>\
**Category:** Support\
**Created:** [October 8, 2022, 7:22am UTC](https://discuss.kotlinlang.org/t/mutablestateflow-for-methods-or-how-to-make-an-observable-function/25763 "2022-10-08T07:22:57Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Psijic](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.kotlinlang.org/psijic/32/2227_2.png) [@Psijic](https://discuss.kotlinlang.org/u/Psijic)\
**Post date:** [October 14, 2022, 12:08pm UTC](https://discuss.kotlinlang.org/t/mutablestateflow-for-methods-or-how-to-make-an-observable-function/25763/12 "2022-10-14T12:08:22Z")

</div>

> [@arocnies](#):
>
> It’s not related to flows but you could use [observable - Kotlin Programming Language](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.properties/-delegates/observable.html)

It looks like last time I used Android’s `Observable`. But in this one I can’t find a difference with a simple setter. I can’t even `.observe()` it. What’s the purpose and how can it provide data to Composable?  
What I need now - is alternative to Android’s LiveData that can be observed and changed anywhere without a coroutine with its `observeForever()`.

---

_[View the full topic](https://discuss.kotlinlang.org/t/mutablestateflow-for-methods-or-how-to-make-an-observable-function/25763)._