Why is over-reusing components bad?
Because each reusable component is an abstraction with a cost. Too many premature abstractions make the code harder to change, since changes ripple through many uses. Balance reuse against the cost of abstraction.
Explore This Question
Search for additional explanations using these tools:
More FAQs in When to Build Reusable vs One-Off Components in React
When the same UI pattern appears in multiple places, like a Button or Card used across pages. Reuse saves repetition and keeps consistency. Extract after you see real repetition, not preemptively.
When a component is used in only one place and has no clear future reuse. Forcing it into a reusable shape adds abstraction without benefit. Leave it as a one-off until real repetition appears.
Primitives like Button are highly reusable across the app. Feature components like Feed are reusable within a feature. Page components are usually one-off, since each route is unique to that screen.
Still have questions?
Browse all our FAQs or reach out to our support team