Hey does LiveData<T>.asFlow create a hot flow?

No. The flow gets activated only when the LiveData if observed. There's also timeout of 5 seconds by default, and the last value of kept for future observers, even after the timeout.

Wow so the livedata still needs a observer. Are you sure?

Oh sorry, I read it the other way around, you're converting LiveData to Flow! THe LiveData will be observed while the Flow is collected. So the Flow will not be hot until you call a terminal operator (like collect or something using it). The source code can confirm all the details, you should be able to navigate to it from IDE.

Btw, what is difference between

hot flow

and

cold flow

?

@Jason A Flow is always cold by design (except it's being collected, but it's only hot for that collector). Here, Robert Keazor was talking about the implementations details of the

asFlow()

extension for

LiveData

in AndroidX Lifecycle LiveData KTX, and if the LiveData would be already observed before the resulting flow is collected, but it's not.

Flow is cold . The simplest way I can explain it , is that cold has a designated start or end, usually at the call site. Like Observable.Just(1,2,3) is cold, because you start it and you know it ends after those 3 numbers are pushed out. But hot can work indefinitely outside the callsite. A simple example of this is View.onClickListener, because you can initialize it in any method but it will continue to work indefinitely until you remove the listener ... That's why Channels and sockets are considered hot by design