This was interesting because, while I have plenty of friends there, his process was totally different from theirs, and design got baked inviolably into the process. We don’t do drawings we specify a key part of the process, and we’ll open bugs against any parts that Engineering doesn’t do right.Ī few weeks ago, I talked to a developer at Garmin.
Perhaps the key reason that I actually call them specifications is that it helps User Experience to be part of the conversation. Figure 1-An example page from a UI Specification We create interactions, not just user interfaces. It has annotations on the left and a table of colors below the high-fidelity drawings on the right. As shown in Figure 1, a UI Specification has both drawings and lots of words, tables, and numbers to tell implementation teams how to get to the drawing and how to make it move. From too much bad experience, I fall firmly on the side of show and tell. There are some obvious practical reasons, mostly having to do with the argument about drawing versus prototyping. A few other designers that I have encountered do similar work, but I am the only one I know of who insists on using that term.
0 kommentar(er)
