ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #realm
Learn how Realm's notification tokens automatically update Android UI components, eliminating manual refresh code while highlighting UI‑thread considerations and cleanup practices.
Realm Results read through to the database instead of copying rows, so offset pagination is usually unnecessary — the real decision is when to freeze a snapshot.
A practical guide to local-only Realm in React Native: schema definition with primary keys, atomic realm.write() transactions, live queries, and safe schema migrations for offline-first apps.
Learn how to design Realm schemas and App Services permissions for Flexible Sync so offline‑first apps sync reliably and avoid costly resets.
Stop using OFFSET and LIMIT for local Realm databases. Learn how to leverage lazy-loaded, auto-updating collections to build high-performance UI lists without manual pagination.
Realm sync reconciles offline edits automatically using CRDT-style merging, but schema strictness and heavy initial sync are the real costs. Here's how it works and how to verify it.
Realm queries return live, auto-updating results instead of static snapshots. Here's how that eliminates UI refresh plumbing, with a Kotlin example and the threading and file-growth caveats that come with it.
A decision guide for Realm schema migration: when to use automatic version bumps vs custom Migration classes, with a production-ready Kotlin implementation pattern and validation strategy.
Realm's live objects and lazy, zero-copy queries mean you never re-query after writes—but thread confinement, invalidation, and file growth trip up most teams. A worked Kotlin example plus the limits that matter.
android
kotlin