Premium
Lift state up vs keep state local in React
A filter drawer, results header, and product grid now need to reflect the same selection state. Would you lift state up or keep it local in each component?
- Lift state up
- Keep state local
What you’ll build / What this tests
This premium react tradeoff battle focuses on Lift state up vs keep state local in React. Commit to a direction, justify it with the prompt constraints, and explain when the alternative wins.
Learning goals
- Who really owns this state?
- Do sibling components need to stay in sync?
- How many places can update the value?
- Will lifting make the parent too heavy?
Key decisions to discuss
- Pick a direction for this exact prompt, not the universal winner.
- State the trade-off that matters most for this scenario.
- Name when another option becomes the better answer.
- Keep the explanation grounded in concrete constraints.
Evaluation rubric
- Strong answers tie the recommendation to the prompt.
- Good tradeoff reasoning explains downsides, not just upsides.
- The answer should show when the recommendation stops being right.
- Follow-up pressure should not break the argument.
Constraints / Requirements
- Which direction would you defend for this prompt, and how would you explain when the other option is…
- Works best when multiple sibling components need the same source of truth and must stay in…
- Stays cleaner when the state is only relevant to one component and does not need to…
Options on the table
Lift state up: Works best when multiple sibling components need the same source of truth and must…
Keep state local: Stays cleaner when the state is only relevant to one component and does not…Common pitfalls
- Arguing from preference instead of prompt constraints.
- Pretending one option is always the winner.
- Ignoring the main downside of the chosen direction.
- Failing to explain when the alternative becomes stronger.
Related questions
Upgrade to FrontendAtlas Premium to access this tradeoff battle. Already upgraded? Sign in to continue.