model-redux-state/design-state-ownership

To decide state ownership in Redux, evaluate whether data is needed globally or locally. UI state stays in components, while shared server-cached data or cross-cutting application data goes into Redux slices to optimize maintainability.

Move data to router state when it must be reflected in the URL, such as active filters or pagination. Router state ownership ensures shareable links and synchronizes view parameters without duplicating data in Redux.

The best way to size Redux slices is grouping related domain data together while avoiding oversized slices. Apply practical heuristics to split or merge slices based on data access patterns and feature boundaries as the app evolves.

Redux state management separates ephemeral form state from server-cached data by keeping local input handling in UI components and storing fetched server responses in Redux, clarifying ownership boundaries to prevent redundant global updates.

You should not use Redux for purely local UI interactions or transient form state that no other component needs. Overloading Redux with isolated component state creates unnecessary re-renders and complicates slice ownership boundaries.