ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Navigator 2.0 replaces push/pop with a URL‑driven page stack. This guide shows how to build a Router that maps URLs to Page objects, enable deep linking, and restore state, plus common pitfalls.
Navigator 2.0 lets you model navigation as a list of pages, simplifying deep‑linking and state restoration. This guide compares it to Navigator 1.0, walks through a two‑screen example, discusses trade‑offs, and gives concrete next steps for developers.
When Compose UI resets to defaults after your app is killed and relaunched, the fault usually lies in remember, missing Savers, or unwired SavedStateHandle. This guide walks through ordered diagnostics, concrete fixes, and escalation criteria.
Learn how to make a Flutter screen survive process death on Android and iOS. The guide walks through enabling restoration, using RestorableInt and RestorableTextEditingController, registering properties, and testing with real device scenarios.
When Android kills a backgrounded Flutter app, users lose their place. This post shows how to use RestorationMixin and RestorableProperty types to keep forms, navigation, and scroll positions intact across process death.
The goal is to restore a Mithril application’s UI state from a JSON backup stored in localStorage while simultaneously re‑establishing the current route and ensuring that the recovered data has not been corrupted. Developers must work within the ~5 MB origin limit of localStorage, avoid a flash of stale UI before the backup is applied, and perform integrity
When Livewire restores a component's state from the encrypted blob, it skips the mount() and directly assigns persisted property values. Consequently, any logic that resides in mount() —such as fetching fresh data from an external source—is not re‑executed, which can leave the component with stale information after a page refresh or navigation. The goal is t
flutter
jetpackcompose
livewire