Should Your Project be an RIA?

April 24th, 2008 by Jason McKinney

Our first Adobe AIR application has been released for about a month and so far has turned out to be a success. Looking back on our three Rich Internet Application (RIA) projects so far (two Flex 2 and one AIR), this one made the most sense as an RIA. Here’s the thought process we’ve gone through when deciding if a project should be developed in an RIA technology:

#1 What’s the Simplest Solution?

We find that the simplest solution is usually the best. This is the KISS Principle, “Keep It Simple, Stupid!” Flex is sexy, but could the same be accomplished using vanilla HTML and CSS?

I’ve seen a general concern on the blogosphere lately that the majority of Flex applications are just rewrites of simple web pages. The most interesting Flex applications are still being released on private intranets, but that’s starting to change. Putting up a simple contact us form in Flex is probably a bad idea. I do think it’s great to rewrite code in another technology as a learning exercise. Just make sure to keep it on your development box.

That’s enough for now I’ll continue with “#2 Worth the Time/Cost?” next time.

Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google

Tags: , ,

One Response to “Should Your Project be an RIA?”

  1. Paul Eident Says:

    Advertising agencies are notorious for using gratuitous use of technology for the “Wow” factor. Most often it is a big mistake and the users suffer.

Leave a Reply

You must be logged in to post a comment.