الحفاظ على حالة علامات التبويب عند التبديل

By default, leaving a tab and coming back rebuilds it from scratch, so your scroll position and inputs vanish. Annoying, right? 😅

A plain navigate replaces the destination, so Compose forgets the old screen. Preserving state means telling navigation to save it instead.

When you pop the old tab, add saveState so its UI state is stored rather than thrown away.

When you navigate to the tab, set restoreState so its previously saved state comes right back.

Together saveState, restoreState, and launchSingleTop give the classic, smooth tab-switching behavior users expect.

For values inside a screen, rememberSaveable keeps things like text fields alive across recreation, complementing nav state saving.

A LazyColumn keeps its scroll when you use rememberLazyListState, and saved nav state lets that survive a tab round-trip.

Always pop up to the same start destination id so the saved-state bundles map back to the correct tab.

Test it: scroll one tab, jump to another, then return. With the flags set, the scroll should be exactly where you left it.

Sometimes a tab should refresh on entry, like a feed. Then simply skip restoreState for that route and let it rebuild.

For data that must outlive even the tab, lift it into a shared ViewModel so navigation flags only handle UI, not your real data.

You kept tabs sticky: saveState + restoreState + launchSingleTop preserve scroll and input, with rememberSaveable backing up in-screen values. Smooth! ✨