Ask two designers to design the same user interface and you will likely end up with two very different designs and interactions on the page. Ask two developers to implement that page and you will end up with different code, too! And that, in a nutshell, is why you need a system.
Have you ever wondered what it takes to build your own design language system? It sounds intimidating, but it's not!
Come to this talk to benefit from our experiences creating and deploying design guidelines from inception to delivering the code that brings the designer's intent to life in real products. Whether you are working with a globally distributed team or by yourself as a freelancer, you will have to confront this issue - do I stop and create a system from scratch, use someone else's, or do something in-between? You will find that a design language system will help you work faster, deliver the basics more easily, and leave more time to get into the hard problems that require concentration and creativity.
We will answer all of your questions:
- Why create a design language system?
- What are the benefits of a design system?
- Should I create a system?
- Who needs to be involved in the work?
- Who are the users of the system?
- How should you manage the work, with competing priorities and deadlines?
- What are the actual steps to define the system?
- How do you get started tomorrow on it?
Attendees will walk away with a clear sense of what it takes to create a design language system and how to get started. They will understand whether to take parts of what we have done or use all of it on their own projects, large and small.
