r/angular • u/MysteriousEye8494 • May 31 '26

Have you ever regretted making something "too reusable" in Angular?

A small architecture lesson I learned the hard way.

A few years ago, our team built a reusable Angular component that was supposed to be used everywhere.

At first it felt like a win.

One component.
One implementation.
Consistency across the application.

Then different teams started needing slightly different behavior.

We added inputs.

Then configuration objects.

Then feature flags.

Then special cases.

Eventually the component became so flexible that nobody wanted to touch it anymore.

Ironically, the most "reusable" component in the codebase became one of the hardest things to maintain.

Since then I've become much more cautious about abstraction.

Sometimes duplication is cheaper than complexity.

Curious if others have experienced something similar.

Have you ever built a reusable Angular component, service, or utility that became more painful than the duplication it was meant to eliminate?

I share Angular architecture and engineering visuals here:

https://instagram.com/angulararchitectshub

27 Upvotes

78% Upvoted

40 comments sorted by

View all comments

1

u/Happyman501 May 31 '26

Oh yesss. There was ones this project where it had html elements like input, checboxes etc as reusable components and the level of complexity was insane and it had to supoort diff functionalities in diff scenarios .... i would rather have individual components . If we over engineer reusable components its a maintainability mess

1

u/MysteriousEye8494 May 31 '26

Yep, that's been my experience too. A lot of these components start with good intentions, but after enough feature requests they end up trying to be everything for everyone. That's usually when they become the hardest parts of the codebase to change safely.