Overall Satisfaction with iRise
My organization is using iRise for product development. I work with product owners and subject matter experts to gather and refine requirements for in-house application builds. Once my IRise prototype is built, our development team uses it to build the application, and our testing team uses IRise to ensure what was built matches what was initially designed in IRise.
- Allows for quick application design
- Enhances requirement gathering and refinement
- Ability to play with large sets of data in order to see the application mirror production
- Enables users to share comments and questions about application builds
- Ability to share prototypes without IRise Reader or the Definition Center would be fantastic.
- Price point is very restrictive. Make it easier for companies to use and license.
- Sometimes IRise has too many special bells and whistles. It's like using a sledgehammer when all you need is a mallet.
- IRise streamlines development and speeds up requirements gathering.
- License fees can be expensive and is usually a prohibitive factor in using IRise exclusively.
- IRise facilities successful product design from start to finish.
I actually prefer Axure to IRise if given a choice due to its price point and ease of sharing prototypes. IRise is easier to use and create prototypes, but the initial setup can be a struggle. Axure is plug and play for the most part. IRise does do a much better job with data-driven products, but most of the businesses I consult with do not care so much about mirroring production.
IRise does a fantastic job of mirroring production. The more data-driven the application is, the more important IRise is in all phases of the SDLC. However, if the business is interested in click-through scenarios with static data, IRise may be overkill and priced too high. Other prototyping software provides the same functionality for a fraction of the price.