FlairBuilder - Interactive Wireframes and Software Prototypes
flairbuilder.com
FlairBuilder - Interactive Wireframes and Software Prototypes
1–10 of 14 posts
Re: FlairBuilder - Interactive Wireframes and Software Prototypes
#2There's a rule-of-thumb when it comes to prototypes that this sorta toes the line on:
Don't make the prototype pretty when the backend isn't done.
Ken Arnold has an at-length discussion of the effect (http://www.artima.com/weblogs/viewpost.jsp?thread=52241).
Balsamiq is great in that regard, since all of the UI controls have a handdrawn look that lowers expectations and keeps people focused on the mockup as an early-stage proposition.
Re: FlairBuilder - Interactive Wireframes and Software Prototypes
#3There's a rule-of-thumb when it comes to prototypes that this sorta toes the line on: Don't make the prototype pretty when the backend isn't done. Ken Arnold has an at-length discussion of the effect ( http://www.artima.com/weblogs/viewpost.jsp?thread=52241 ). Balsamiq is great in that regard, since all of the UI controls have a handdrawn look that lowers expectations and keeps people focused on the mockup as an earl…
If I was going to this level I'd probably just use Flex itself. I also think that Balsamiq has the right concept in terms of level of detail.
Re: FlairBuilder - Interactive Wireframes and Software Prototypes
#4There's a rule-of-thumb when it comes to prototypes that this sorta toes the line on: Don't make the prototype pretty when the backend isn't done. Ken Arnold has an at-length discussion of the effect ( http://www.artima.com/weblogs/viewpost.jsp?thread=52241 ). Balsamiq is great in that regard, since all of the UI controls have a handdrawn look that lowers expectations and keeps people focused on the mockup as an earl…
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!
Re: FlairBuilder - Interactive Wireframes and Software Prototypes
#5There's a rule-of-thumb when it comes to prototypes that this sorta toes the line on: Don't make the prototype pretty when the backend isn't done. Ken Arnold has an at-length discussion of the effect ( http://www.artima.com/weblogs/viewpost.jsp?thread=52241 ). Balsamiq is great in that regard, since all of the UI controls have a handdrawn look that lowers expectations and keeps people focused on the mockup as an earl…
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, EVERYTHI…
Hey, 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
Re: FlairBuilder - Interactive Wireframes and Software Prototypes
#6There's a rule-of-thumb when it comes to prototypes that this sorta toes the line on: Don't make the prototype pretty when the backend isn't done. Ken Arnold has an at-length discussion of the effect ( http://www.artima.com/weblogs/viewpost.jsp?thread=52241 ). Balsamiq is great in that regard, since all of the UI controls have a handdrawn look that lowers expectations and keeps people focused on the mockup as an earl…
If I was going to this level I'd probably just use Flex itself. I also think that Balsamiq has the right concept in terms of level of detail.
I it fine when you have the expertize to create coded prototypes, but unfortunately this is not the case always.
Re: FlairBuilder - Interactive Wireframes and Software Prototypes
#7There's a rule-of-thumb when it comes to prototypes that this sorta toes the line on: Don't make the prototype pretty when the backend isn't done. Ken Arnold has an at-length discussion of the effect ( http://www.artima.com/weblogs/viewpost.jsp?thread=52241 ). Balsamiq is great in that regard, since all of the UI controls have a handdrawn look that lowers expectations and keeps people focused on the mockup as an earl…
Hmm.. The Uncanny Valley effect for UI prototypes :)
Re: FlairBuilder - Interactive Wireframes and Software Prototypes
#8It's a pretty cool app. However, I would advise the developers to put text descriptions under all the icons, because it is not clear what the the icons do, and it is a pain to have to hover over them to find out.
Re: FlairBuilder - Interactive Wireframes and Software Prototypes
#9It's a pretty cool app. However, I would advise the developers to put text descriptions under all the icons, because it is not clear what the the icons do, and it is a pain to have to hover over them to find out.
Labels for each component is a good idea and I'll consider it.
As the set of components will grow, it may become easier to just enter a few letters in the search box to filter down the options. I am also thinking about putting in the front somehow the most used components.
Re: FlairBuilder - Interactive Wireframes and Software Prototypes
#10It's a pretty cool app. However, I would advise the developers to put text descriptions under all the icons, because it is not clear what the the icons do, and it is a pain to have to hover over them to find out.
Labels for each component is a good idea and I'll consider it. As the set of components will grow, it may become easier to just enter a few letters in the search box to filter down the options. I am also thinking about putting in the front somehow the most used components.
Apple do something similar with interface builder. If you have a mac, check it out.
Good luck with the project. It looks like a really cool bit of software.