Re:From idea to core prototype in hours, not weeks
by seanmcdirmid on Sunday February 23, 2014 @08:40PM
(#7288651)
I'm a bit confused by the article's blurring of design and prototyping boundaries. Is it reasonable (i.e. useful) to convolute wire framing with prototyping? I once worked as a prototyper for a design studio, and to them prototype meant an approximation of the product that could be used for critique and evaluation with users (so maybe a lofi paper prototype, deck-like click-thru prototype, or even a quick/dirty application).
[ Parent
| on HN ]
Re:From idea to core prototype in hours, not weeks
by williamnewton on Sunday February 23, 2014 @08:47PM
(#7288667)
Is it not clear that my approach is to 1. map out the idea (wireframing) and then 2. hack together a prototype?
Re:From idea to core prototype in hours, not weeks
by seanmcdirmid on Sunday February 23, 2014 @09:12PM
(#7288735)
Your post mixes together wireframing with prototype hacking. But I guess this is to be expected when programmers are doing design, a designer would look at this very differently.