# Google just released AppState — is it actually better than SharedViewModel for shared state? — retained record

> Retained reddit record from reddit:androiddev.

Canonical: https://highsignal.app/data/records/9fced46c9cfb5af7

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:androiddev)  published 2026-10-30 21:24 ingested 2026-10-31 02:36

[original source ↗](https://www.reddit.com/r/androiddev/comments/1xjruub/google_just_released_appstate_is_it_actually/)

## retained text



```
Google released AppState and it looks like a cleaner way to handle shared state than passing a SharedViewModel around. I never really liked SharedViewModel, felt like one screen ends up owning data other screens depend on it.

From what I get so far: StateStore is a shared observable value, MutableStateStore is the writable one, AppState owns the lifecycle, and transform lets you derive state automatically instead of syncing stuff by hand.

 Curious what people think of the API so far.

**Docs**: https://developer.android.com/topic/libraries/architecture/appstate

**Video**: https://youtu.be/69QYEXymfVo

Anyone planning to try it out?
```



document fetched 2026-10-31 00:19 · canonical https://reddit.com/r/androiddev/comments/1xjruub/google_just_released_appstate_is_it_actually
