The Integrity Design System was mostly built out of necessity. As a designer, you can build and design whatever you want….but as a UI/UX designer you have the extra weight of efficiency and consistency. You cannot design what cannot be built. So Integrity was born.
Again, Integrity started with a doc. I design on purpose, meaning every design has a central mission and goal, Integrity’s goal was to maintain the integrity of design consistency through every single product. Its an atomic design system, built on the material design language with around 50 different components stemming from only 10 base components. Any new design can be created from these “elements” much like legos.
Having to quickly compose screens across multiple different vendor applications quickly and nimbly takes a design system flexible enough to design nearly anything and elemental enough to do it quickly. As new designs were built, new components were added to the canon.
Regrettably, Integrity never officially made it to an official code repo. I won’t say it was never coded, Integrity’s designs have been committed to code plenty of times. However, there isn’t a central library of components on a production server somewhere as I originally intended. Design is a siloed practice in an organization with low-design maturity and it becomes difficult to turn a design system into product or practice without organizational buy-in or when the senior developers leave for greener pastures. In the end, it’s hard to kick against the pricks.
