medium10 pts · first answer countskotlin-flowandroid-architecture

Exposing UI state from a ViewModel

An Android ViewModel exposes screen state (loading, content or error) to a Compose screen. Which type is the usual choice, and why?

A.A SharedFlow with replay 0, so a screen that starts collecting after rotation waits for the next change before it draws anythingB.A Channel, so each state value is consumed exactly onceC.A LiveData created inside a coroutine on every callD.A StateFlow, because it always holds the latest value and gives it to new collectors immediately

Discussion 0

Join free to post in the discussion.

Exposing UI state from a ViewModel

Discussion 0

Related questions