- Here’s a question I’ve heard a few times recently: – “What if we create a component library in React/Vue/Angular/whatever and a new component technology replaces it?”
That’s not a question of if. It’s a question of when. These technologies have become wildly popular, but they’re not the end game. Like all technologies, something better will eventually come along…
Here’s a question I’ve heard a few times recently:
“What if we create a component library in React/Vue/Angular/whatever and a new component technology replaces it?”That’s not a question of if. It’s a question of when. These technologies have become wildly popular, but they’re not the end game. Like all technologies, something better will eventually come along and replace them.
But that fact is largely irrelevant. Establishing a library of reusable components for your company today remains absolutely critical.
Move Faster TodayReusable components help your team move faster by creating higher level abstractions. Components eliminate decision fatigue by programmatically enforcing a standardized approach. Just consider an opinionated form TextInput component.
It can eliminate all the following decisions:
Should I put the label above the input or beside it?Should I display validation errors to the right or below the input?What color should the error be?How should I mark required fields?Should I validate required fields on blur or upon submit?How much padding should I place between the label and the input?The list goes on. These aren’t questions your designers and developers should be asking every time they create a new form.
Enforce ConsistencyReusable components enforce user interface consistency. Your company likely has many developers. Yet your job is to build an app that looks like it was built by one developer.
To do that, it’s critical to use reusable components. Copy/paste isn’t a design pattern. If designers…