Designing Ente Locker gave me room to explore. But when I put the screens together, individually reasonable choices began to contradict each other. Every fix meant revisiting earlier work.
I needed a shared set of decisions that could hold the product together.
02 / The first component
It started with a button.
Rounded corners survived Locker’s iterations because they felt friendly and approachable. I carried that into the buttons, then learned to build variants and nested components around repeated needs.
Old and new button libraries, from my original write-up.Open image ↗
03 / The foundations
Make the decisions reusable.
I brought colours and text styles into the system, then revisited their names when they became hard to trace. A component library only helps if its foundations are understandable.
The updated Account and Backup designs use the same header, menu rows, icons and rounded containers. The destructive action keeps its own colour within that shared structure.
New flows kept exposing missing components and states. Reviewing established systems helped me see those gaps. The result is a working library that continues to evolve, rather than a finished set of rules.
