Home
BYTE Newsletter
Keep up with all the BYTE News and Reviews

Subscribe
Serdar Yegulalp

Serdar Yegulalp



Mobile Office: Partial Functionality Not Enough

Comments | Serdar Yegulalp, BYTE | November 08, 2012 08:31 AM

Category: Tablets, Smartphones, Operating systems, Notebooks

The rumors were true: Microsoft has versions of Office coming for the iPhone, iPad and Android, all slated to be released in early 2013. That said, don't ditch your Intel- (or AMD-) powered notebook just yet: we've got a long way to go before all of Office is that portable.

The Verge recently reported taking a sneak peek at editions of Microsoft Office for various mobile platforms. But based on what they're reporting, what we're getting -- at least at first -- amounts to little more than a Microsoft-sanctioned document viewer.

Office Mobile, as it's called, is quickly shaping up to be little more than a read-only front end for an Office 365 subscription. Some editing features are going to be enabled in the product, but if Office 365 itself is any hint, they're not going to have a fraction of the functionality found in the Microsoft Office we all know and use. It's little more than an officially-branded reader, a way to get people on board the train.

In time it could gain more sophisticated functionality. But what about now? What's ironic is how Microsoft has, in a way, already created and released a mobile version of Microsoft Office that's fully compatible with its full-blown counterpart: Office for the Windows RT edition of Microsoft Surface. It's not feature-for-feature identical to the x86/x64 edition, but it's close enough that vastly more people will feel comfortable with it than they will with what Microsoft currently has planned for Android or iOS.

The people who use Office a lot -- I include myself in that number -- take its feature set seriously. Excel, for instance: if you're a diehard Excel buff, can you imagine living without pivot tables, or any of the other super-crunchy CPU-intensive features that would make a mobile device slow down to a grinding crawl? And even if you opt for the RT edition of Office, you're still not all the way home. Among other things, Pivot tables can be used on the RT version of Office, but not created or edited -- and you need to be a licensed Office 2013 organization to use Office RT legally in a business setting.

Office RT might be the most capable of the Office-on-mobiles products, but there's a long list of Office features it doesn't support:

  • No macros, add-Ins, forms, or custom programs (Word, Excel, PowerPoint).
  • No send email features (Word, Excel, PowerPoint, OneNote).
  • No automatic SkyDrive sync integration (Word, Excel, PowerPoint).
  • No editing equations with equation editor 3.0 (Word, Excel, PowerPoint).
  • No "Lync file download" because there's no Lync on RT (all the more remarkable because there is a Lync for iOS.)
  • Word only: no grammar checking for certain language versions of Office (it's a long list -- 15 languages). Spell checking and other proofing components are available for more languages.
  • Excel only: No creating data models.
  • PowerPoint only: No SharePoint slide library ActiveX control, no support for certain legacy media formats, no PowerPoint flash video playback, and no recording narrations.
  • OneNote: No audio and video recording from within OneNote, no importing a document through an attached scanner, and no keyword searching in embedded audio and video.

People who only need casual document editing, even on mobile devices, now have plenty of options, many of them free: OpenOffice, Office Web Apps, Google Docs, you name it. Even iOS itself comes with Office document viewers, pitifully weak as they might be. There's no shortage of this stuff out there, and the quality of it has improved markedly over the past five years. But none of it is a substitute for the breadth of features in full-blown editions of Office, many of which you only retrospectively realize you needed. I wouldn't want to make an investment in a "Mini-Me Office" where change tracking no longer worked, or where font choices no longer showed up properly, or my style declarations didn't apply, or ... you get the idea.

Shoehorning any desktop app into a mobile form factor is always a dicey proposition. Limitations on device space, processing power, screen real estate, and the functionality of the platform all stack the deck against you. This isn't limited to productivity apps like Office, either. Consider Google Chrome for Android. It only bears a passing resemblance to its desktop counterpart, but attempts to make up for this by allowing back-end synchronization of your bookmarks and recently-visited pages. I don't have trouble using it, mind you, it's just that I can see why it had to be so radically reworked to be a mobile app.

Right now, a fully-mobile, fully-featured version of Office is either impossible or impractical. But that only poses a problem for the people trying to bring such a thing to market, not existing Office users. Those who take Office seriously will stick with the hardware -- and software -- they've become comfortable with to get their work done, and those who only need a limited subset of features haven't made themselves dependent on Office anyway.

We're still a long way from someone offering a serious mobile alternative to Office as we know it, and what Microsoft is planning isn't about to change that.

Follow Serdar Yegulalp and BYTE on Twitter and Google+:



Related Reading


More Insights




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

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE 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. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

COMMENTS

Tune In to BYTE
Facebook Twitter LinkedIn Newsletter RSS
Whitepapers
whitepaper
In this paper you will learn the five trends shaping the future of enterprise mobility. Learn how the rise of social media as a business application, the lurring between work and home, the emergence of new mobile devices, the demand for tech savvy employees and changing expectations of corporate IT will fundamentally change the workplace.
whitepaper
In a survey of more than 1,700 information workers (iWorkers) in North America, notebooks, desktops, and smartphones were found to be “must-have” devices, while tablets, slates, and netbooks were relegated to “nice-to-have” status, according to a commissioned study conducted by Forrester Consulting on behalf of Dell and Intel.
Sponsored by: Dell
Upcoming Events