When a design is handed over to the developer, there’s multiple layers of information that needs to be conveyed. In addition to the Mockups and Specs+Assets, one must also share the Interactions, Copy, and a Checklist. All these cover different aspects of the design solution and need to be collated in one, simple, accessible document that sits on the cloud. You can call it the Design Handoff Document.
TABLE OF CONTENTS
| Table of Contents |
|---|
Mockups
Naming your files : Let the file/screen name not possess any form of versioning. The name of the screen should simply describe it’s function. If you’re not yet using a version control solution for your designs, you probably should.
Plus, make sure you use consistent casing when naming your screens, whether it’s ‘camelCasing’ or ‘Sentence casing’ or ‘lower casing’ etc.Have the necessary, archive the rest : At the time of handoff, you’d have collectively zero’ed on an option you’re going to build. So weed out all the older iterations & explorations. It also helps you write simpler filenames.
...
For example, raise a Jira ticket against the responsible developer the moment you spot a discrepancy in the build. This way there’s organized accountability within a timeframe and no email escalations against the designer.
And ...
When sharing your Specs, don’t forget to communicate to the developer the Grid System you’re using in your designs. I use 8-point grid system considering almost all the screen-sizes in the market are divisible by 8. Here’s how you can start using it in your designs.
If your designs involve a lot of state-changes for buttons or labels, then be sure to document passive/active states of your buttons, up/down states, dynamic text, animation from variables, etc.
...