Combining Techniques: State Down + Content Up
What you'll learn: How to use moving state down and lifting content up together to eliminate unnecessary re-renders without any memoization overhead.
The Power of Both Patterns
You've learned two structural refactoring techniques separately: moving state closer to where it's actually used (state down) and passing stable content as children (content up). When you combine these patterns, you create the most efficient component architecture possible—one where updates naturally stay isolated without needing React.memo, useCallback, or useMemo at all.
How They Work Together
Moving state down reduces the scope of re-renders by placing state in the smallest component that needs it. Lifting content up keeps expensive UI trees stable by passing them as props (especially children), which don't change when the wrapper component's state updates.
Used together, state changes trigger re-renders only in tiny, focused components, while the bulk of your UI remains completely untouched because it's props that were created higher up in the tree—where no state changed.
The Mental Model
Think of it like organizing a warehouse: you keep the busy, frequently-moved items (state) in a small, easily accessible area (tiny component), while the heavy, stable inventory (expensive UI) stays in the main warehouse untouched. You're not adding locks or security checks (memoization)—you're simply organizing space efficiently so movement in one area doesn't disturb the other.
Real-World Application
Apply state-down to contain the state change, then wrap that small stateful component inside a parent that receives expensive UI as children. The state updates only re-render the wrapper, not the children.
Key Takeaway: Combining state-down and content-up gives you the performance benefits of memoization without any of its costs—no dependency arrays, no comparison overhead, just clean component architecture that naturally prevents wasteful re-renders.