The design is not the spec

The purpose of a design file is to gain consensus not tell developers what to build. A design file should be included with a functional specification as supporting information to help a developer visualise the output of the code they are writing. Because, no matter how much you use Auto-Layout or variables, a design file1 is a snapshot of a site in a single state — usually the happiest of happy paths. They do not typically include enough information for a developer to build a fully functional application without resorting to (a) estimation, (b) guesswork, and/or (c) pestering. Design files are useful, they have a definite purpose. A design file is an excellent tool for alignment; show it to various stakeholders for them to agree on (and, please make sure your development partner is one of those stakeholders). It removes some level of ambiguity when everyone thinks of the particular feature. See also, consistent naming of components. Pharma websites particularly require approval before…