Conclusion first: NestDirect's Saved page now updates each "↓ $X since saved" badge the moment a landlord changes the rent. It opens zero new Realtime channels and makes zero extra fetches to do it. The interesting part was not the wiring. It was one ordering rule that stops an older read from overwriting a newer one.
Last month I shipped a live nav badge. saved (3↓) counts saved listings whose rent dropped below what it was when you saved them. A Supabase Realtime subscription on UPDATE public.listings pushes rent changes to it.
The Saved page did not get the same treatment. It fetched once on mount. So a renter could sit on the Saved page and watch the nav say 3 drops while the header on the page said 2. Two views of the same fact disagreed, which is worse than both being stale.
