The answer
Because it creates a giant root component and excessive re-renders across the tree. Lift only what siblings genuinely share; keep state local where it is only used by one component or branch.
Common State Management Mistakes in React UI Apps
Why is lifting all state to the root a mistake?
More FAQs in Common State Management Mistakes in React UI Apps
Because it creates two sources of truth that drift apart. When the prop changes, the copied state does not, causing bugs. Keep one source of truth and let the parent update it.
No. Compute them during render from props and existing state. Storing derived values causes sync bugs when the underlying source changes and the stored copy does not update.
No. UI flags belong in local component state, not global state. Putting them in Redux or Context adds complexity and re-renders without benefit, since they are only used by one component.
Still have questions?
Browse all our FAQs or reach out to our support team
Want to upskill yourself?
Your learning library
Small steps. Big possibilities.
Find your next course. Build something great.