# @codingambitions on Instagram

- **Type:** Image
- **Original URL:** https://www.instagram.com/p/DeCPqTXH484
- **Gondola URL:** https://gondola.cc/posts/71122500-codingambitions-instagram
- **Thumbnail:** https://img.gondola.cc/tr:w-,h-,fo-auto/postThumbnails/497f1cb594.jpg
- **Posted:** 2026-10-03T14:11:51.000+00:00
- **Account Owner:** Android Developer - Jetpack Compose,Kotlin Multiplatform,Flutter (@codingambitions) — https://gondola.cc/codingambitions

## Caption

Still writing Parcelize or boilerplate custom Saver implementations just to survive process death in Jetpack Compose? 🛑

Most Android devs know remember() and rememberSaveable(), but rememberSerializable() is the unsung hero if you already use
 kotlinx.serialization.

Here is the best part: it doesn't do a slow JSON string roundtrip! As explained by Google's Marcello Galhardo, it uses a custom codec that serializes Serializable classes directly into Android Bundle types.

Swipe through the carousel to see: 
👉 Why rememberSaveable gets messy with pure data classes 
👉 How rememberSerializable() cleans up UI code 👉 How to use the saved delegate directly in SavedStateHandle 
👉 Full comparison matrix

Drop a comment: Which one do you find yourself reaching for the most in your current codebase? 💬

Save this for later. Want more content like this? drop it below in the comments.

FOLLOW FOR MORE codingambitions

#jetpackcompose #android
#programming #androiddeveloper #kotlin

## Stats

- **Views:** 0
- **Likes:** 0
- **Shares:** 0
- **Comments:** 1

## Tags

programming, jetpackcompose, kotlin, androiddeveloper, android

---
Copyright (c) Gondola