Guidebook Beacon UI Kit
Formalizing Guidebook's app UI
|Additional design||Guillermo Mont|
I created a UI Kit for Guidebook for both iOS and Android - Beacon. This served as a tool to quickly build and iterate on both of our client apps.
As the design team grew, it became immediately obvious that we needed a way to store, version, and organize our design files. We played around initially with using GitHub to store our sketch files, but quickly realized that it was both too slow and too opaque to use as a true home for a design system or UI kit.
I decided to use Abstract as the system of record for our design files. Not only could you preview Sketch files through the browser or their mac app, it also used git under the hood for robust and proven versioning. While it took the team some time to get used to the workflow of git, it eventually led to us having a much more organized and logical system in place to store our UI.
The UI kit itself is nothing revolutionary, but was built to help us more rapidly iterate and build upon existing designs. The gains from standardization due to formalizing your UI can't be understated - it made interfacing with our developers simpler development speed increase exponentially.
From an structure standpoint, we initially started with a single component library with all of our UI components living inside. This ended up becoming incredibly bloated and slow, so we broke each component out into a separate
[comp] file which helped with both speed and merge reconciliation. It also helped us reason easier about any individual component. The downside of this approach is that Sketch library updates enter a massive cascade, which can lead to confusion or errors.
While the system did allow for more atomic level components, in general designers were inputting higher order components into individual view files. We found that cheaper, higher order components helped with iteration and reusability.