markpetrowsky.com

Last week I attended my first Chicago IxDA group event. The topic was RIA’s (Rich Internet Applications): what are they, how do you define them, etc. The monthly discussion is only the second the IxDA chapter has held, and on my first attendance my impression was very positive. Some interesting conversation came about, and overall I thought it was definitely a worthwhile way to spend a school night.

A couple interesting questions from the session:

1. Does an RIA have to exist in a browser window? For example, is iTunes a Rich Internet Application? iTunes pulls from the web so does that justify calling it an RIA?

2. Are dynamic Flash sites RIAs? If the site pulls data from a CMS and you have a very rich visual interface does that constitute a site being an RIA.? Is the Wilson Sporting Goods site, for example, an RIA?

3. How do we break from the multi-”page” based design approach and start designing for more single-page apps with multiple “states”? When conceptualizing RIAs what processes and deliverables will help communicate the vision to clients and developers. Are static wireframes still feasible methods to communicate the vision or do we need to do more, such as create prototypes or animated storyboards?

4. Just because a site uses AJAX is that enough to say it’s an RIA? Isn’t there more to consider than just the technology?

5. Is the term “Rich Internet Application” temporary nomenclature we use now to describe the ability to perform tasks in the browser that mimic what traditional desktop applications have been able to do for years?

Rich

Module windows, smooth animated affects that help convey information, and drag and drop functionality make the applications rich.  Rich applications have the ability to do in the browser what has been possible in the desktop world for years. Maybe living in a browser is part of what defines RIAs at this point in time.

Internet

I feel just because a traditional desktop application downloads information from the web it doesn’t necessarily mean it’s an RIA. I doubt many would consider Adobe Photoshop an RIA even though it does automatic updates via the web. However, iTunes depends on data feeds from the Internet so it blurs the line because it’s only usable when wired in. Maybe the key is Internet dependability. Can the application function when disconnected from the cloud?

Application

Is pushing data or an experience enough? Maybe to be classified an application requires that a user be able to contribute, manipulate, or create with the tool?

Perhaps in a few years RIA will be clearly defined but now the definition is still fuzzy.

Categories: Chicago, Web, Design. You can leave a response, or trackback from your own site.