I have frequently written and commented about Enterprise RIA’s, here and elsewhere. One of my concerns in relation to RIA is terminology, and I’ve asked around for idea’s about a more appropriate name – to no avail. Yet, my colleagues did relate to it and brought up a few ideas and findings.
You might want to have a look at Ofer Spiegel’s blog posting on the topic. Also Amit Ben-Zvi recently summarized a discussion on this topic that a group of us had recently, trying to define the application context best suited for Enterprise Rich Internet Applications. We identified 5 key attributes, which need to be present simultaneously in order to qualify a good context for a RIA:
- The users are away from the office, and require remote (Internet) access
- The application is actually a stateful process, is highly interactive, and requires a rich and dynamic front end with many data fields. If a static HTML form is good enough for the process then look no further – but if it is a dynamic form that keeps changing according to the input provided then RIA might be appropriate
- The application should be a core process for the organization (e.g. CRM, finance/ERP, marketing, inventory)
- Requires on-line connectivity/synchronization
- It is a centralized process with significant human interaction
We did find, though, a pretty broad consens in differentiating Enterprise from Consumer RIA’s: the “Richness” in Enterprise RIA’s is first and foremost about the interaction, in contrast to Consumer RIA’s which focus essentially on Rich Media output (which brings me back to propose to use different terms for Enterprise RIA and Consumer RIA ).