Commentary

Serdar Yegulalp
 

On Giving Away Microsoft Office

There are a few ways to see Microsoft's plans for a free web-based version of Office. One, it's self-competition; two, it's competition with open source software; three, it's competition with other web services. Which one matters most?

There are a few ways to see Microsoft's plans for a free web-based version of Office. One, it's self-competition; two, it's competition with open source software; three, it's competition with other web services. Which one matters most?


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The first one's not hard to understand. Why would someone pay for a full-blown version of Office when they can get a sizeable chunk of the functionality for free in a web browser? They could, but the web browser is still a pretty lousy application-delivery platform. My own experience has been that when people have a choice between a "fat" local client (which may not be all that "fat", actually) and an in-browser application, they go for the local app for the sake of not being constrained by the browser's quirks and modalities. New browsers don't so much solve the problems as push them off into a corner.

That brings me to item #2: OpenOffice (dot org). Rather than compete with OpenOffice by releasing a slimmed-down free version of Office -- say, just Word, without the dictionaries or spell checker / grammar tools and maybe some of the other pro-level, server-needed features -- Microsoft is providing hosted apps. And here, again, I'd rather choose the local client than the web-based one. There's a lot about OpenOffice that I don't like, but I'd rather put up with those limitations than the ones I get in a browser-hosted app.

#3 is fairly obvious: with stuff like Zoho and Google Docs popping up, Microsoft's obliged to compete and not lose too much market share to them.

As you can guess, it's the degree of competition from OpenOffice that I'm most concerned with. My own experience has been that I was able to replace most, but not all, of Office 2007 with OpenOffice. I still use Word and Outlook; OpenOffice Writer still lags badly behind Word in a lot of respects and doesn't show any signs of catching up soon, and there is no replacement for Outlook in that suite anyway. But I haven't bothered with Excel or PowerPoint or all the rest of them, because the OO editions of same more than cover my needs. It's the stuff specifically in Word and Outlook -- where I spent a lot of my workday -- that I paid to have access to, like a robust grammar checker.

This, then, is how I see Office losing to OO or other such programs: not in big strides, but in tiny nibbles. A free web-based version of Office won't stave off that kind of lossage, since free-on-the-web simply isn't the same as free-on-the-desktop by any measure.

But the door revolves in both directions. OO stands to lose users to for-pay programs if the price is reasonable enough and the prospect of paying for things you can't have at any price in OO (like a decent grammar checker) is strong enough. Microsoft's not taking all this lying down; there's no reason OpenOffice should assume just delivering free is enough. They need to market themselves as intelligently and broadly, by providing the core for free and asking a modest price for a selection of things that truly matter to people. I don't think they want to become the WordPerfect of 2010, but that's where they're headed with their current if-you-build-it-they-will-come approach.

InformationWeek Analytics has published an independent analysis of the next-generation Web applications. Download the report here (registration required).

Follow me and the rest of InformationWeek on Twitter.


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