> So, in all the responses I've gotten, I've seen "RIAs are > not for you then" "RIAs really don't make for good > e-commerce". So my question is: When is an RIA justified? > When is there a benefit to create an RIA over an HTML > application?
I don't know if there's a bright line that'll be easy to distinguish in all cases, but in general, I'd argue that rich client applications are better than HTML applications if you want to approach the kind of functionality you have in desktop applications. For each project, this may be more important or less important than other factors, of course. > In the responses I've gotten, there has only been one Pro, > the optimization of bandwidth. I think the other is quite > obvious, although left unsaid, aesthetics. I think that the biggest advantage is simply that you can provide more functionality, and make it easier for the end-user to use your application. To me, that's much more important than aesthetics. For example, a while back we had an HR project that involved an organizational chart. Now, everyone in the business world has a pretty good idea of how an org chart works already, so the best interface for managing such a thing would be one that follows that existing idea. Well, you don't want to be doing that in HTML, let me tell you. Yecch. On the other hand, it's an ideal use for Flash - drag-and-drop elements within a recognizable org chart interface. > So far I my list of cons is: > - More expensive to develop > - Requires more developers I think this is true, to a certain extent. I think that in many respects it's harder to design Flash interfaces, or VB interfaces for that matter, than it is to design HTML forms. Of course, I think that this is largely because those interfaces can do more. > - No application consistency This doesn't have anything to do with Flash, and everything to do with good/bad design. > - Requires a plug-in ... that's almost universally installed, and pretty easy to install if you don't have it already. > - Initial Load Times Increased Dramatically I think this is generally accurate; I found the same thing to be true when building JavaScript/DHTML interfaces that cached data on the client. I also think this is outweighed by the increase in responsiveness and usability that you get over the course of the application's use. > - Requirements for internet connection and computer speeds > increased I don't think either of those is necessarily true; I can run Flash applications on my Pocket PC, which isn't a speed demon. > - We rely on a sole company to continue and support the > technology (MM) rather than a consensus (WC3) *No one > can buy the wc3 and discontinue HTML No one can buy the SWF file specification, either, as far as that goes, so this is a pretty minor concern to me. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
