Well, the thing is that sales are low for me. Here in Romania we have such an young entrepreneurial culture that we just start learning how to build and sale our products. I'm so keen to learn more and more. I've been working hard in the past year to build this product, but yet I need to learn so much more about promoting and selling it.
If more people find out about my product, than more will take advantage of my "free for non-profit" policy.
Plus, I'm planning to share all my knowledge with my fellows Romanian starting entrepreneurs. Through blogging, video interviews, podcasts etc. Romania has a potential to go beyond the outsourcing destination label, and I'll be happy to bring my contribution.
Does offering free licenses of my product to non-profit orgs counts? In the past year and a half, I've given more than a few dozens of licenses to organizations, schools or people who simply could not afford to buy a $99USD worth license. I haven't kept a strict list of all licenses given away. I usually give and forget.
You can't imagine how much I'd love to see Peldi and Jason Cohen speaking! :-)
I plan to offer support for grid based design, but since positioning is absolute in FlairBuilder, I wonder how could you generate CSS based layout. I'll keep this in mind as it's definitely an interesting idea!
FlairBuilder is more than a simple drawing tool, or than a tool that lets you add simple navigation to your wireframes.
Every component you put on a page in FlairBuilder is a fully functional component. Buttons, text boxes, checkboxes etc. are working like real components (as they are in fact real components). FlairBuilder aims for the same interactivity as coded prototypes, but providing you the means for creating prototypes faster, in a visual manner, and with no coding.
In the future, I plan to offer the same collaborative workflow that protoshare has to offer.
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.
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.
If more people find out about my product, than more will take advantage of my "free for non-profit" policy.
Plus, I'm planning to share all my knowledge with my fellows Romanian starting entrepreneurs. Through blogging, video interviews, podcasts etc. Romania has a potential to go beyond the outsourcing destination label, and I'll be happy to bring my contribution.