The Case for Writing Your Own Component Library

A component library makes sense when it captures things the product repeatedly needs. It makes less sense when we spend weeks anticipating components before there are screens to put them on.

I'd start with a few real uses and let the differences show up. Then we can decide what belongs in the shared API. Maintaining the library is work as well, so somebody needs time to deal with changes after the first set of buttons is finished.