SavedStateHandle vs. rememberSaveable: Which One Should You Choose?

 A senior developer's guide to clean state management in Jetpack Compose—where to store your data and why it matters for app stability.

SavedStateHandle vs. rememberSaveable: Which One Should You Choose?

TL;DR:

  • SavedStateHandle: Use for Business/Presentation State (IDs, search queries) in the ViewModel. It is the most reliable anchor for process restoration.
  • rememberSaveable: Use for Pure UI State (scroll position, animation toggles) in the Composable.
  • Rule of Thumb: If losing the state breaks the screen’s logic, use the ViewModel. If it only resets a visual preference, keep it in the UI.

1. The Architecture Gap

In a modern Jetpack Compose app, state lives in two distinct layers. Choosing the wrong bucket leads to “State Leakage,” where your business logic becomes tangled with your UI or your UI becomes unresponsive after a background kill.

SavedStateHandle (The ViewModel Layer)

This is your Architectural Anchor. It allows the ViewModel to interact with the system’s saved instance state. Because the ViewModel is the link between your UI and your Repository, this is where the “Intent” of the screen belongs.

rememberSaveable (The UI Layer)

This is your Visual Polish. It exists entirely within the Composable function. It behaves like a standard remember, but hooks into the same Bundle mechanism.

⚠️ Reliability Nuance: While both use the same underlying Bundle, SavedStateHandle is generally more reliable for restoring state across full process recreation. rememberSaveable only restores state if the Composable is still part of the restored navigation backstack.

2. Key Comparison: Head-to-Head

Press enter or click to view image in full size
Key Comparison: Head-to-Head

3. Real-World Decision Matrix

Scenario A: The User’s Search Query

Decision: SavedStateHandle

Why? The search query is the “trigger” for your data fetching. If the query is stored in rememberSaveable, your ViewModel won't know what to reload after process death. It will sit idle until the UI finishes its first composition and "pushes" the query back to the ViewModel.

// In ViewModel: Query is restored immediately
val searchQuery = savedStateHandle.getStateFlow("query", "")

Scenario B: An “Expanded” State for a List Item

Decision: rememberSaveable

Why? Whether the third item in a list is expanded doesn’t change what data the Repository provides. It’s a visual preference. Keeping this in the ViewModel leads to “State Bloat” — where your ViewModel becomes a dumping ground for every checkbox.

// In UI: Visual state stays in the UI
var isExpanded by rememberSaveable { mutableStateOf(false) }

Scenario C: Form Input Fields

Decision: SavedStateHandle (Usually)

Why? Use SavedStateHandle when the form involves validation, business rules, or must survive process death with high reliability. Simple, unvalidated forms can stay in the UI, but rememberSaveable is not a substitute for proper state architecture in complex flows.

4. Don’t Break the Binder

Regardless of your choice, both tools funnel into the same underlying Bundle. This means the ~1MB Binder transaction limit is your shared enemy.

❌ The Mistake: Saving an entire API response or a large object.

✅ The Senior Move: Store only Primitive IDs.

// Store only the ID
val userId = savedStateHandle["user_id"] 

// Re-fetch the heavy data from Room/Cache during recreation
val user = repository.getUserFlow(userId)

5. ❌ Common Pitfalls to Avoid

  • The “Dual State” Trap: Don’t save the same piece of data in both places. This leads to “Source of Truth” conflicts where the UI thinks the search query is “A” but the ViewModel thinks it is “B.”
  • Forgetting the Saver: rememberSaveable can't save custom classes unless they are Parcelable or you provide a custom Saver.
  • Backstack Blindness: Remember that if a Composable is removed from the navigation stack, its rememberSaveable state is usually cleared. SavedStateHandle persists as long as the ViewModel is alive.

🏁 Final Thoughts

Choosing between these two tools is about responsibility. If the data changes what the user sees (the content), put it in the ViewModel via SavedStateHandle. If the data changes how the user sees it (the layout), keep it in the UI with rememberSaveable.

If your app can’t survive process death, it isn’t production-ready.

💬 Join the Conversation

  • Do you prefer keeping all state in the ViewModel to make it a “one-stop-shop” for testing?
  • What’s your strategy for handling custom Savers in Compose?

📘 Master Your Next Technical Interview

Since Java is the foundation of Android development, mastering DSA is essential. I highly recommend “Mastering Data Structures & Algorithms in Java”. It’s a focused roadmap covering 100+ coding challenges to help you ace your technical rounds.

Comments

Post a Comment

Popular posts from this blog

No More _state + state: Simplifying ViewModels with Kotlin 2.3

Image
 Clean up your Android code with Explicit Backing Fields—the modern way to handle read-only state without the boilerplate. TL;DR:  Kotlin 2.3 introduces  explicit backing fields , allowing you to replace the classic  _state  +  state  boilerplate with a single, cleaner property—provided you're okay with a few experimental trade-offs. If you’ve been developing Android apps, you know the “Backing Property Dance.” It’s that repetitive ritual where we create a private  MutableStateFlow  and a public  StateFlow  just to ensure encapsulation. The “Old” Way (The Boilerplate) private val _uiState = MutableStateFlow(UiState.Loading) // Exposing a read-only view of the mutable internal state val uiState: StateFlow<UiState> = _uiState.asStateFlow() We’ve done this for years to prevent external classes from mutating our state. While effective, it pollutes our IDE suggestions with underscores and adds unnecessary ceremony to every singl...
Read more

Why You Should Stop Passing ViewModels Around Your Compose UI Tree 🚫

Image
 Master State Hoisting and the "Route-level" pattern to build scalable, testable, and preview-friendly Android apps. If you’ve been building with Jetpack Compose for a while, you know how tempting it is to just pass a  ViewModel  instance down through five layers of UI components. It’s convenient—one object gives you all the data and all the functions you need. But here is the architectural reality:  Passing ViewModel instances deep into your UI tree is an architectural anti-pattern.  It couples your visual components to business logic and makes your code significantly harder to maintain, test, and preview. The Core Problem: Lifecycle and Scoping ViewModels are designed to be state holders tied to a specific lifecycle (usually a Navigation Destination). When you pass a ViewModel into a small UI component, you break the  Unidirectional Data Flow (UDF) . ❌ The “Bad” Way (Tight Coupling) // ❌ BAD: This component is now impossible to preview or reuse @Composabl...
Read more

Is Jetpack Compose Making Your APK Fatter? (And How to Fix It)

Image
 Unpacking the Compose Tax, compiler-driven DEX optimization, and why your resource strategy must evolve for modern UI. TL;DR DEX Bloat:  Compose’s compiler injects “Restartable” and “Skippable” logic for memoization; R8 minification is effectively required. Code vs. Assets:  Moving iconography to  ImageVector  constants allows R8 to prune unused assets as code. Tooling Leak:   ui-tooling  in release builds is the #1 cause of "false" bloat. The Scale Factor:  Compose has a higher “size floor” but a much lower “size ceiling” than the legacy View system. The promise of Jetpack Compose was simple: “Write less code, ship faster.” But as teams migrate, a quiet concern often echoes in code reviews:  “Why did our APK size just jump?” While Compose removes the weight of deep XML hierarchies and the overhead of ViewBinding, it introduces a unique “Compose Tax.” For a senior engineer, the goal isn’t just to accept this tax, but to optimize the runtime...
Read more