Picture Pedalpost, a bike-courier app (invented for this post). One fact, “the courier is standing at a customer’s door,” has to be true in four places at once: the dispatch screen, a foreground service, a home-screen widget, and a notification action. Add a battery-saver flag, a zone filter, and an order feed, and you have the usual Android state mess:
A combine(...) call that grows a sixth upstream and loses its typed overload.
A MutableStateFlow<UiState> that wakes every collector when a single field changes, or a pile of separate flows that cannot be updated together.
A singleton, a SharedPreferences file, and a SavedStateHandle that each claim to own "the current delivery" and quietly disagree after process death.
Timers and notifications buried inside collectors, with cancellation rules nobody can recite.
Jetpack AppState attacks this from a direction that surprises people: it takes Compose’s snapshot state…
