Thanks for the feedback Angel! I've discovered and experienced everything you stated, unfortunately though, after we bought it! :)
The product is an amazing prototyping tool, no doubt about that. But it is only as good as how much interaction you can build into it, or are willing to build into it. Intranet sites are perfect for the tool because of the nature of a site: page driven, page states, server hits, static content, less form controls, etc. But when we start prototyping applications with the tool (webapps) the amount of interaction that we can accurately display falls quite short to what we actually build. Like Angel said, you are limited by what form controls iRise gives you. It does not handle state-less or page-less application design. All of the interactions in the tool assume a server hit (form submission). But aside from the negative, we are using it, and we are using it with success. It is forcing us to rethink some of our app designs to make them work in the tool, but we are gathering great feedback when people use the simulation that iRise produces. Instead of building out a lot of html code and writing additional code to make it work without a backend in place, we are testing iRise simulations in our usability lab. Yes it is expensive, and I do not have any numbers to show the value, but it is proving useful in our large enterprise. Rob ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
