How the Cloud is Failing Mobile Workers
Incompatibility is pervasive in the mobile cloud
The basic issue is that services used by cloud-based apps don't run on mobile browsers. Why that's the case is unclear; WebKit anchors the iOS, BlackBerry OS 6, and Android OS 2.21 browsers, and the same goes for desktop Safari and Chrome. Microsoft's and Google's cloud-based productivity apps run on desktop Safari and Chrome, as well as on IE and Firefox. However, in mobile Safari, mobile Chrome, and the BlackBerry WebKit browser, they can do very little; usually, they're limited to viewing documents.
Because of these problems, mobile users will have broad compatibility issues beyond the cloud apps in Office 365 and Google Docs. Many websites often don't work correctly on mobile browsers. As a result, mobile users end up with Web pages they can't scroll through, cutting off the information. Until last Friday's update, Google Calendar suffered from this issue, and the Office 365 beta's Outlook management console has the same problem.
Mobile users will also discover that websites using the widely adopted, open source Tiny MCE editor bars them from entering or editing information in rich-text fields. (If you see iconic buttons for boldface, italic, paragraph formating, and the like in a website's content fields, that's Tiny MCE.) The popular Drupal content management system depends on Tiny MCE, as does Office 365's community support forum. Drupal lets you switch to a pure HTML view that's a pain to use but at least provides editing access; Office 365 has no such option, so mobile users can't post or reply to its help forum's content.
These issues are emblematic of the concerns that Apple, Google, Microsoft, and Research in Motion should be addressing on the mobile side. They should be helping Tiny MCE be mobile-compatible. They should be designing their websites to work on the mobile browsers, not just the desktop ones. That means both updating their mobile browsers to offer the same capabilities as their desktop equivalents and using neutral, compatible technologies. Ironically, Microsoft Office 365's SharePoint admin console works just fine on an iPad, even though SharePoint editing controls do not -- because Microsoft used Java for the console but an incompatible option for the users' editing controls.
Until cloud applications work with mobile websites, mobile users will have to depend on local apps and file transfer via email, local syncing, or (ironically) cloud storage services. For example, cloud storage services Dropbox and Box.net let multiple users access the same files via their shared-folder capability. Mobile users can access files from a common repository available to an entire workgroup; download them to their mobile device for editing in iWork, Quickoffice, or Documents to Go; and finally upload the revised files back to that shared folder. You can do the same with Google Docs' shared-files capability, buit not with SharePoint Online, which supports only downloading to mobile devices, not uploading back.
As a productivity platform, the cloud makes the most sense for mobile users, who by definition are not at their desks and don't have the internal resources they would at the office. Yet the productivity apps for that same cloud are aimed at desktop and laptop users, not mobile users. If this continues, we may see a real irony: Those who work in a fixed location use cloud apps on PCs, while those who are on the go end up using local apps on their smartphones and iPads. Isn't that dumb?
This article, "How the cloud is failing mobile workers," was originally published at InfoWorld.com. Read more of Gruman et al.'s Mobile Edge blog and follow the latest developments in mobile technology at InfoWorld.com.