In the mid-Nineties, when the Filofax was battling with Lotus Organizer for the title of King of the PIMs; as the PC industry was blooming and before the days of Apple Stores, a device so cool it was like something from science fiction began to get some buzz. The Apple Newton.
Of course, there was no way I could afford one of these mythical things, so I opted for the next best thing: the Amstrad PenPad. In January 1995, when an Apple Newton was weighing in at around £700 (a lot of money for an underpaid IT Manager!) the Amstrad PenPad could be had for less than £100. You get what you pay for, and for reasons that will become clear, it was consigned to the bottom of my work bag within a month of purchase.
The spec on this thing was amazing. For a handheld device. Of the time. Boasting 40 hours battery life, handwriting recognition for calendar, contacts, tasks, meeting notes and Other Things, the PenPad had a capacity of 330 full pages of addresses (“Full” pages, mind you!) or 6000 diary entries.
You could expand the storage (to a whopping 2mb) via a PCMCIA slot on the underside; but you were only able to write to the internal storage or the PCMCIA card; there was no dual usage. There was no wifi, so sharing was done manually – in other words: you printed stuff via the serial cable interface on the top.
The first time I turned up to a meeting packing my PenPad, my colleagues were green with envy… until, that is, I actually tried to take notes. The handwriting recognition system still didn’t recognise my handwriting, despite hours of supposed training to get it to do just that. I’d input all of my contacts and thought the crappy recognition was all part of the device’s learning process!
After retraining the thing twice more, and even going as far as to adapt my handwriting in an effort to suit, it just wasn’t working and my Penpad’s days were numbered.
Despite it’s failings, I’ve kept it, boxed with manual and handy multi-language help stickers since then! (What can I tell you? I’m a pack rat – which is why I’ve still got a boxed copy of Windows v1.03, too!)
OK, I’ve shared my “dodgy gadget purchase” story; it’s time for you to ‘fess up and share yours – even if you bought the Sega 32x.
(thanks to China Guccio for the Newton photo, used under Creative Commons)
TechCrunch is carrying a post by MG Siegler, who points out that Microsoft are using Google-owned YouTube to host videos that are going after Google’s low cost apps and email. In it, he says
Another key selling point [according to Microsoft]: if you choose to use Google Apps, your formatting may be screwed up when you inevitably have to work with others who are using Microsoft Office. When all else fails, turn to FUD.
This isn’t FUD. When it comes to collaborating with Microsoft Office users, Google Apps (and Zoho Writer, for that matter) do screw around with formatting.
Like many people today, I’m looking for work, so I’m sending my CV/résumé out several times each week to recruitment agencies. Most recruiters and job sites will insist on having CVs sent to them in Word format, so I have to export my document as a .doc file.
And there’s the problem: a document that looks fine in Google Docs can be all over the place when it’s saved as Word document. Inconsistent tab- and line-spacing; random hieroglyphic characters in place of bullet points; disobedient font sizing are just some of the problems I’ve encountered.
It would be great to be at a point where I could simply share a link to my CV with a recruiter, a job site or an HR department, but we’re not; Microsoft’s Office document formats are still what most businesses use today. My CV is usually my first means of introduction to a prospective employer, so there’s just no way I can afford for it to look untidy – it would be like turning up to a job interview with breakfast down my jacket.
If there’s one feature that cloud-based word processors absolutely must get right, it’s making sure that exporting to the most widely-used document format works faultlessly.
I was fortunate enough to score an invite to the Google Wave preview today, and remembering back to when I watched the keynote from this years Google IO conference in May this year, it was clear then that Wave is way ahead of it’s time:
Before I go any further, I want make one thing clear having been glued to Wave all day: I think Google Wave is awesome; it is the future of email and collaboration. The thing is, it’s too far ahead of it’s time, and that’s what will hold it back from large-scale mainstream penetration, which is why Outlook is safe. For now.
I don’t want to add to the blogosphere’s echo-chamber with my own review of the hows, whys and wherefores, so instead:
For a good taster of the technology behind Wave, I’d recommend taking a look at this article,
And, for a good example of how forward thinking organisations like SAP are already looking to leverage the collaborative power of Wave, take a look at the video embedded at the bottom of this post.
Again, let me be clear: I think Google Wave is awesome; it is the future of email and collaboration. The interface looks just like Gmail, except it feels slicker; this might have something to do with the Google Web-Kit front-end, but I’ll leave smarter people than me to comment on that. By way of a quick fly-by, you get your folders on the top-left, contacts on the bottom left; Inbox in the middle column; Active message (“wave”, in parlance) in the right-hand pane. New waves (messages) appear in your Inbox, just like any other email program, except, when you look closely, they’re changing. All the time.
The unread message count (circled in red) is incrementing, and new text creeps across the subtitle of the waves.
This indicates changes, made in realtime, to that wave; or new “blips” (new conversation strands) being added. Realtime, on-the-fly collaboration is quite something to watch – updates, edits and annotations appearing and changing as quickly as you can visually process them. The power of this platform hits you like a, well, like a wave crashing against the shore. Once more, lest you forget my feelings, I think Google Wave is awesome; it is the future of email and collaboration.
Ok; it looks nice; it’s feature rich and it’s generally pretty darn cool. So, why do I say Outlook is safe for a while?
I’m reasonably attuned to dealing with a realtime feed (thanks to Friendfeed), but even now there are times when I do need to hit the pause button. If I take off my rose-coloured, early-adopter geek glasses for a moment, and, instead, put on my “project manager with too many projects” glasses or my “HR advisor in the middle of a round of mass redundancies” glasses, imagining the volume of data that “regular” users are expected to act upon every day, Wave turns into a tidal surge.
Although it’s been described as email on steroids, I actually think Wave falls short right now. It’s too noisy. Where Wave does land some heavy punches is against Sharepoint – which, by the way, is a great product, if so-called implementors would take the time to refine it beyond its out-of-the-box install – creating FAQs, procedures and wiki-like pages was never, easier, more dynamic, or downright fun.
However, if I were to introduce Wave to a “regular” business with regular users as a replacement for Outlook today, those users would Freak Out. Look at today’s version of Outlook – it gives those stressed-out users the tools to control their Inbox; they can prioritise their actions and activities based on keywords, filters and search terms. (Once more, I think Google Wave is awesome; it is the future of email and collaboration.) With Wave, I can’t do that; it all pours in. What’s lacking at the moment is control and filtering of the of the incoming feed.
Yes; I understand that Wave is a preview right now, but, Wave was introduced to the world as “email, invented today”, and as such, it needs to demonstrate to decision makers in “regular” businesses that it can live up to that promise.
One last time, I think Google Wave is awesome; it is the future of email and collaboration but until Wave can give users the same sense of control, management and prioritization of their Inbox that Outlook does, I reckon Outlook is safe; but not for long.
(Footnote – my grateful thanks to Steven Hodson, whose recent post, inspired my use of the “emboldened point emphasis” in this article)
Recent Comments