A Google Docs outage and a reminder of Google's mobile innovation mastery compete for our attention in the same week.
Dear Google, our relationship is getting a little complicated. You've never been a company that technology pros love to hate, in the way that many genuinely hate Microsoft, Apple, Oracle, or ever more frequently these days, Facebook. While we've had our privacy fights in the past, you've made your feelings clear. You've made our mobile lives easier, saved us money, and made consumerization of IT practical. But here's the problem: Once we love you, you have to be solid.
As Thomas Claburn notes in his no-nonsense column for InformationWeek.com, it takes just an hour-long outage of Google Docs, as happened Wednesday, to remind us: Google made a significant mistake. The company did not ensure that full offline storage and editing was available for Google Docs right from launch.
"The company recently introduced limited offline functionality, so you can store a limited number of Gmail messages, Docs files, and Calendar entries locally and access them when there's no network connection," Claburn notes. But offline editing? Not yet. Google had offered offline editing via its Google Gears technology for a while, but hasn't made sure users got this power back, Claburn writes.
We know software crashes. But a continuing problem for Google with enterprise IT is that when the cloud service is down and the user can't get the work done, he feels utterly stuck--as stuck as a man or woman waiting by the phone, powerlessly, hoping for a phone call to go on date number two.
As Claburn notes, this offline editing functionality is a no-brainer. Why hasn't Google done it?
Now on the flip side, as Eric Zeman points out, mobile technology users have many reasons to love Google and the Android OS. Yahoo's identity woes, punctuated by the firing of Carol Bartz this week, remind us how few companies are pushing mobile innovation as fast and hard as Google, Zeman writes.
AOL and Yahoo have pushed mobile to the back of their priority lists, and that's a shame, Zeman says. We need more Googles to ensure innovation, and to ensure rivalry, he argues, persuasively.
"Not that there aren't a million substitutes for what Google offers," Zeman writes "There are thousands of applications that are available to each and every smartphone platform to fill the gaps. The problem isn't the gaps so much as it is the integration and--even more so--the need for competition."
Few companies have taken the mobile risks that Google has. That's not good news for anyone who uses or manages mobile technology, because as InformationWeek editor-in-chief Rob Preston notes this week, great innovation requires risk.
So Google, we technology users and leaders are willing to make the relationship work. Please don't keep us waiting by the phone.
Laurianne McLaughlin is editor-in-chief for InformationWeek.com. Follow her on Twitter at @lmclaughlin.
See the latest IT solutions at Interop New York. Learn to leverage business technology innovations--including cloud, virtualization, security, mobility, and data center advances--that cut costs, increase productivity, and drive business value. Save 25% on Flex and Conference Passes or get a Free Expo Pass with code CPFHNY25. It happens in New York City, Oct. 3-7, 2011. Register now.
SaaS As Innovation Driver?Software as a service is the clear No. 1 way enterprises consume cloud. InformationWeek's SaaS Innovation Survey reveals three tips to get the most from SaaS: Make it a popularity contest. Have an escape plan. And remember that identity is the new perimeter.
Top IT Trends to Watch in Financial ServicesIT pros at banks, investment houses, insurance companies, and other financial services organizations are focused on a range of issues, from peer-to-peer lending to cybersecurity to performance, agility, and compliance. It all matters.
Join us for a roundup of the top stories on InformationWeek.com for the week of October 9, 2016. We'll be talking with the InformationWeek.com editors and correspondents who brought you the top stories of the week to get the "story behind the story."