Inputs

by Dmitry Trostin

At YClients, I was trying to create the simplest and most consistent design system possible. Why? First, the business demands consistency. Second, I believe everything should have a clear purpose. The world already had enough design systems that only differed by colors and border radius. Spoiler: it had just 4 text styles. That turned out to be more than enough to build even the most complex and content-heavy interface screens for any scenario.  More on that next time. Today — inputs. Before I joined, the team was using dozens of different input types, all with different styles and behaviors. I reviewed them all and came up with a simple and elegant solution: one master-mega-input that included all possible elements. All child inputs had to do was hide what they didn’t need. Same on the frontend: build one, and then just tweak space tokens when needed.