The Prop Drilling Threshold
What you'll learn: How to decide when prop drilling becomes painful enough to justify introducing Context.
The Judgment Call
There's no magic number, but here's a practical guideline: If you're passing props through 2-3+ intermediate components that don't use them, Context starts looking attractive.
The Sweet Spot for Props
Props work beautifully when:
- Data flows 1-2 levels deep
- Intermediate components actually use or transform the data
- The relationship between components is clear and direct
// Totally fine — only one intermediate layer
<Parent user={user}>
<Header>
<UserProfile user={user} />
</Header>
</Parent>
When Drilling Hurts
The pain emerges when you're building "prop tunnels":
// Getting annoying — 3 layers just forwarding
<App user={user}>
<Layout user={user}>
<Sidebar user={user}>
<Navigation user={user}>
<UserMenu user={user} />
</Navigation>
</Sidebar>
</Layout>
</App>
Layout, Sidebar, and Navigation don't care about user — they're just messengers. That's your signal.
The Threshold Factors
Consider Context when:
- 3+ forwarding layers exist
- Multiple props are being drilled together
- Many sibling components need the same data
- Refactoring becomes risky (adding a prop means touching 5 files)
The Analogy
Props are like hand-delivering mail room-to-room. That's perfect for nearby rooms. But when you're passing mail through three floors of people who don't read it, install a pneumatic tube system (Context) instead.
Key Takeaway: When 2-3+ components act as pure pass-throughs for props they don't use, you've crossed the threshold where Context reduces complexity rather than adding it.