Build your Sketch Library for fast prototyping
Draw your design on paper, take pictures and import to prototyping tool, add link to each page, show it to the stakeholder and they will give you this face 🧐.
Paper prototyping can be rough, abstract, and hard to understand. So… you to want build high-fidelity prototypes? Here are some problems:
- You need to spend a lot of time on design decisions, not on solving the real problems.
- Product requirements change faster than your prototype; what you designed would be trashed before it gets presented to product owners.
How about trying to build a faster high-fidelity prototype next time, with powerful Sketch Libraries.
A quick look of Sketch Libraries
What is Sketch Libraries?
Sketch Libraries are just ordinary Sketch documents that contain Symbols. However, Libraries are cross-document symbols, which means you can use these symbols across all your Sketch documents.
Why Sketch Libraries matters?
- In order to keep your design consistent in different design files, especially when you start collaborate with other designers. You need a single source of truth to relay on. What you changed in the Library will also change in other files.
- You probably used other online wireframe tools to do rapid prototyping. If you think about it, those tools are just libraries which contain all the components you need to build a prototype quickly. So why not just build a one by yourself?
Build your first Sketch Library
When you start building the sketch library, it’s more like making(not playing) Lego. It’s not the fun part, but it’s a very important step.
Just like Lego, one library can use another library to build a more complex one.
Sketch has a document about how to build the library, and I would recommend starting there. Here are some tips for when you are building the library.
Mono Library or Multi-Library
Mono library includes all the components in a single file. The benefit of mono libraries are: It’s easy to mange, as only one file is needs to be imported into Sketch Library. However, when your library starts growing, it’s also can be hard to maintain. Another reason to avoid mono libraries is that your symbols selection in Sketch will be huge (although you can of course use plugins to insert symbols).
One good example is Atlassian’s Web GUI pack
Multi-library makes each file smaller, and it is easier to maintain in the future. There are also drawbacks: If one library uses another library, both libraries need to be updated. In Kotti Design, we found that the multi-library architecture is more suitable for us.
Take a look of Kotti Design System — Sketch Library
Structured Nest Library
Sketch allows nested symbols, so we can use this feature to build a nested library. Kotti Color is in the bottom of the hierarchy, and Kotti Icon and Kotti Typography rely on it. It makes changing the color of icons or text easier. Other components depending on Kotti Icon and Kotti Typography makes quickly changing the icon and font type super fast.
The End…
We start building our first library when Sketch launched this feature. We spent around a few days to convert all the symbols into libraries. Yes, it’s a tedious process, but the benefits are huge:
- For small features (2–3 views), we can build the prototype in 2 hours, and can be used for collecting customer feedback.
- For projects, we still using paper prototype in the early stage for fast design iteration. Then we switch to Sketch — Full Speed On.
