Repository source: docs/plans/archive/ios_users_page_cache_freshness_step1_solution_assessment.md
iOS Users Page Cache Freshness Step 1 Solution Assessment
Problem Statement
iOS users need the users page to show fresh state instead of stale cached content. Source: thread-20260826030018-109bf96b, submitted 2026-08-26T03:00:18Z.
Option A: Disable static caching for the users page
Pros:
Directly targets stale user listings.
Simple to reason about.
Low product ambiguity.
Cons:
Reduces cache benefit for a read-heavy page.
May mask broader cache invalidation bugs.
Option B: Keep caching but add stronger freshness/version invalidation
Pros:
Preserves performance while fixing stale state.
Aligns with existing version-bypass behavior.
More reusable for other stale-page reports.
Cons:
Requires careful reproduction on iOS.
More moving parts than disabling cache.
Option C: Add a visible manual refresh control
Pros:
Gives users immediate recovery.
Small UI addition.
Cons:
Does not fix incorrect freshness behavior.
Adds burden to users.
Recommendation
Recommend Option B.
Brief justification:
The issue is likely cache correctness, so preserving caching while tightening invalidation is a better default than turning the page dynamic.