Design Handoff and Collaboration Guide
January 21, 2019
Let’s imagine that you just finished preparing designs for a mobile app. You’re ready to give these designs to your engineering team.
This part of the design process is called “the handoff”.
Why is the handoff so important? Engineers need precise ways to understand designs and to translate them into code, so it’s important for us to generate our designs in a way that is modular, redlined, formatted, and easy for your team to understand.
As a designer, it’s good to have a process for design handoff that considers the needs of your product team to facilitate collaboration whether you’re a small start-up or a tech giant.
In this course, we’re going to outline how to use Zeplin to facilitate design handoff by taking designs and automatically exporting them into a format that generates code snippets, style guides, specs, and assets for everyone on the product team to access.
This course is created in collaboration with the Zeplin Team. Zeplin lets you handoff designs and styleguides with accurate specs, assets, code snippets—automatically!
Zeplin is offering Commonlounge students first 6 months free! Enter your email address here: https://hi.zeplin.io/commonlounge and then sign up at https://app.zeplin.io/register
Module 1: Hand Off Best Practices
In this module, we’re going to cover what you will want to consider when designing your hand off process.
- Lesson 1: Save Time By Automating Spec Prep
- Lesson 2: Make It Easy For Your Team To Access Assets
- Lesson 3: Use Version Control
- Lesson 4: Have a Single Source of Truth
- Lesson 5: Use Shared Style Guides & Components
- Lesson 6: Automate Communicating Updates
Module 2: How to Get Started with Zeplin (Coming soon!)
You’ve covered handoff best practices and how to share a design system. Now let’s show you how to roll up your sleeves and get started with Zeplin!
To get notified when this module becomes available, please make sure your are enrolled to the course.