“Using Zeplin has created more time for our team to experiment with designs, as opposed to manually creating design spec documents. Our engineers prefer not having paper or PDF spec documents, instead they can reference designs on-screen.” –Jason Stoff, Sr. Designer at Starbucks
You’ll want to save time preparing specs by automating as much of the speccing, redlining, and asset preparation processes as possible. This is where a design handoff tool comes in.
Before handoff tools existed, designers would print their designs on paper, draw redlines with a pen, and hand the paper to their engineer. The good news is you don’t have to do that anymore. 😅
Now, redlines, specs, and code snippets can be automatically generated using Zeplin by uploading your file from Sketch, Photoshop, Adobe XD CC, and Figma.
Zeplin automatically redlines your file and converts...
Lesson 2: Make It Easy For Your Team To Access Assets
3 min read
In the past a few years, a lot of different screen sizes and measurement units emerged across iOS, Android, and Web platforms.
We need to consider this and make it as easy as possible for our teammates to access assets in the right format for their platform so that they can start development, so that we don’t have to manually reproduce assets for the right platform, and so that we don’t get caught in back-and-forth email chains last minute while engineering is trying to make a sprint planning deadline.
iOS engineers use pt (points) as their main development unit. This is different from the typographical ‘point unit’ that is available to us in our design tools.
Android engineers use dp (density-independent pixel) as the main unit and sp (scale-independent pixel) for text size.
In Web, there are even more options. Some engineers simply use px (pixels), some use percentage values, and some of them use em/rem values. Both rem and em are relative units, px is not. Relat...
“We basically consider Zeplin to be our source of truth for collaborating with Engineering. If it’s not in Zeplin, it’s not official.” –Jason Stoff, Sr. Designer at Starbucks
Top product teams use a single source of truth to communicate final product changes across multiple stakeholders. A lot of teams like to use Zeplin for this because it’s great for sharing final designs.
Shannon Tinkley, a Product Designer at Slack, shares how she uses Zeplin to communicate the lifecycle of her designs to her team.
“Once concepts are in a more solidified state I push my screens out to Zeplin. Each of my Zeplin projects are based on feature flows. This way the whole team gets their eyes on it nice and early and allows us to nail down things that might have been previously overlooked. From there we just continue to iterate and tweak, and the n...
Every design has a story, countless iterations behind the scenes. Designers keep updating their designs before and after they’re implemented. The rest of your team may get lost within these changes and may not know which version to use.
Commit messages communicate what has been changed in...