Choosing between Redux-style single stores, atom-based state, and server-state caching in large iOS apps.
A large iOS app uses a single Redux-style store (e.g. TCA/ReSwift) holding deeply nested arrays of server entities. Screens re-render on unrelated updates and reducers grow unwieldy. Which change most directly addresses BOTH the performance and the maintainability problems at scale?