<@UFT11FKSP>, why have you chosen to implement your own Observable value, instead of using StateFlow...

# kvision

[y9san9]

@Robert Jaros, why have you chosen to implement your own Observable value, instead of using StateFlow?
Only because you don't want to require coroutines with your lib or there are other reasons?

[Robert Jaros]

It's been implemented before StateFlow was available.

[Robert Jaros]

And now I try to keep coroutines dependency optional, because it adds a lot to the final bundle size.

[y9san9]

Thanks for answer

[Tomas Kormanak]

@Robert Jaros What is you preference for state management now?

[y9san9]

There are a custom lib class

[Robert Jaros]

I will probably use StateFlow for next project.

[Robert Jaros]

Currently I'm using redux-kotlin and it works very well.

[Tomas Kormanak]

Thank you, I am considering both, but I haven't decided yet. Any pros and cons?

[Robert Jaros]

I would really like to understand flows better 🙂 It would be easier to draw conclusions 😉

[Robert Jaros]

e.g. to be able to use precise and optimized data bindings I've implemented ObservableState.sub() extension function and it is very simple implementation

[Robert Jaros]

But I've also created StateFlow.subFlow() extension for the same purpose, but I have no idea how it works 😉

[Tomas Kormanak]

Thanks, finally we are going with StateFlow.