Commentary

Chris Murphy
Editor, InformationWeek  

Rich Internet Apps: On The Road To Must-Have

The relentless pressure of the Web goes like this: One year something's a cutting-edge feature on Google or Amazon, the next people expect it on their 401(k) site, and soon employees wonder why it isn't on the company intranet. IT leaders should know that the use of rich Internet applications are well into that cycle now, with 44% of companies using them, our most recent research finds.

The relentless pressure of the Web goes like this: One year something's a cutting-edge feature on Google or Amazon, the next people expect it on their 401(k) site, and soon employees wonder why it isn't on the company intranet. IT leaders should know that the use of rich Internet applications are well into that cycle now, with 44% of companies using them, our most recent research finds.Rich Internet apps are Web-based apps written to run with the snap of desktop software, and they can make sites far more engaging and useful -- or end up as expensive eye candy that doesn't serve a business goal. This article spotlights the business and technical problems that can make the difference. And it looks at the different ways companies are building them, from increasingly rich Ajax platforms to big-vendor options such as Adobe's and Microsoft's.

Rich Internet apps might sound like nice-to-have glitz in today's uncertain U.S. economy. No way. Our research shows companies are half as likely to kill a customer-facing project right now as one that doesn't touch the customer, and it's customer-facing uses where rich Internet applications are most often applied.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

That's why I look for the momentum building behind RIAs to continue. Let us know what's happening in your companies when it comes to spending on Web enhancements such as rich Internet applications.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links