3 ms·
Totally agree! One of the most annoying things is when you see a design that is called a "prototype" but it looks like a BADLY done final design. A prototype
by zaidf 18y ago
Totally agree!
One of the most annoying things is when you see a design that is called a "prototype" but it looks like a BADLY done final design.
A prototype needs to CLEARLY be a prototype and that is where balsamiq is awesome. If it does not look like a prototype, then I won't know what elements of the design are bad because of your TASTE in design and which are bad because this is a PROTOTYPE.
In general, EVERYTHING in a prototype should be up for judgement IMO. Don't want people to be judging the colors? Don't put it in the prototype! Don't want people debating how the checkbox should look? Don't spend time delicately designing the perfect checkbox!
- ccpascu 17y agoHey, Cristian here, developer of FlairBuilder. It's true that early in the process is not OK to spend to much time on details. You'll just want to grab a pencil and a sheet of paper (or a digital equivalent as Balsamiq Mockups) and sketch down as many ideas as you need. However, there is a point/stage where you'll need to dig down into the details, as many as possible to make sure, again as much as possible, that you got the requirements right. Another thing: IMHO there is a clear difference between an wireframe and a prototype. With both you can go from plain, or even sketchy look'n'feel up to a polished design. FlairBuilder aims to bring the amount of interactivity that coded prototypes have (for proper usability and user feedback ), with the plain simple look'n'feel of wireframes. Cheers, Cristian