The POS Assets Library
Overview
For the team, the initial intention to build the the design system was to help scaling; given at that time, it seems there are more similar projects to come. By building one like this, it would help the process to build one much faster.
​
However, this is my point of view as an apprentice at the time.
Team:
Kenny Ho [Lead Visual]
Phuong Le [Lead Experience]
Hung Tran [Designer]
Duration:
April 2019 - June 2019
Introduction
While I together built with other design leads the Milano POS system, I get to learn as an apprentice, that tidy and consistent design trumps in design. By building a single source of truth, everybody can easily onboard with the system (both designs and developers) and communicate the same language.
This leads to the primary outcome for this procedure: recycling components, which clear and instructional guideline. However, I personally wouldn't call this a design system per se. It was rather a Style Guide and a UI Component Library combination.
The Foundation
While it wasn't my execution to come up and direct the guideline, I got to start it early. It all came down the functions and features that come up in the system, then break them down to the atom element. The starting point was basic assets such colors and fonts, alongside with atom and molecules components such as buttons, cards, types of forms, and filters, and etc.
And for an apprentice like me, learning how to build a design system is a great entry to learn how design ought to work. During the process, I get to learn how I should always stick with consistencies and recycling, and not creating new elements, assets or new components.
And for an apprentice like me, learning how to build a design system is a great entry to learn how design ought to work. During the process, I get to learn how I should always stick with consistencies and recycling, and not creating new elements, assets or new components.
Documentation
This ought to be the step that happens right after the curation step. Every elements need to be categorized and layout rule as soon as possible. However, given the constraint time of the project, there was lots of miscommunication whether about use cases, rules and labels of assets. Yet, while trying my best to catch up with the deadlines, it is crucial to document because it will be important for those onboard the project.
Scaling between platforms
Designing between mobile and tablet was a bit struggle for me. Initially, when we first built, it was a lot harder since we built for mobile first, then scale later to larger screens devices. However, later in the development, we shift to tablet first. Hence the design was still easier to breathe for me.
Setbacks and Lessons
Lots of setbacks since I haven't gotten any chances to measure the outcome of the design, since by the time I finished, the app still also hasn't been deployed. On the other hand, as an apprentice, it helps me learning a lot about designing systems.