gleb a — Wed, 30 Dec 2009 11:39:45 GMT

I think the idea behind the article is really good. if the specs include both the technical part and the graphical part, if they are written in plain language rather than technical cliches, this is a good way to start a development process.
As for gui prototypes, I think they serve a good purpose, when client draws a lot of attention to detail, or when you don’t want to have any arguments post factum…. when it’s all written on paper, and signed off by both parties, it’s much easier. If the client does not like the way ui prototypes look, it makes sense to provide design mockups too. this way expectations can be managed in a smart way.
as for the “add widget button” vs “way to add widgets” problem, I think it all depends on what kind of client it is. I for one prefer the “add widget button” option for the specs (provided it’s been confirmed with client that he wants this solution specifically). at least this is the way we do it. Gleb, www.specshelp.com

Boxes and Arrows: Comments by gleb a