The ‘bet on webOS’

Handpicked

Earlier today I was reading this brief piece on This Is My Next, titled Why HP killed its webOS devices, and while what Cathie Lesjak (CFO of HP) claims makes sense, I still fail to grasp the general logic behind HP’s strategy regarding webOS.

From the article:

To put it simply, the TouchPad and webOS devices failed to meet HP’s financial targets and unit sell-through expectations. And HP failed to “position webOS as the clear number two platform for tablets.” According to Cathie, HP’s “bet on webOS” would result in an even larger loss in Q4 if the company continued business as usual […] 

Ms Lesjak adds:

To make this investment a financial success would require significant investments over the next one to two years, creating risk without clear returns. […]

As I said other times, I’m not an analyst, and business strategy is definitely not my field. But simply as an observer, I can’t help wondering what HP was thinking all along since the Palm acquisition, and also why HP decided to acquire Palm in the first place. This ‘bet on webOS’, how did HP expect would pan out? 

They showed the TouchPad, the Veer and the Pre³ at the Think Beyond webOS event in February (and the photos taken by Engadget during their liveblogging well capture the atmosphere of a company which apparently believed in its products); the presentation was entertaining and, I’d say, rather well orchestrated (especially since it heavily borrowed from Apple’s keynotes). They teased the audience only to announce that those three fantastic devices would have been available ‘in the summer’. First mistake. 

The first of those three products to be available was the Veer, launching on AT&T on May 15, arguably the least powerful, attractive or interesting of the three. Second mistake.

Then the TouchPad, finally available on July 1, only in the USA. July and August, from what I’ve observed, are by far the slowest months of the year. Did HP really expect the TouchPad to be an exceptional success during this time of year? Third mistake. 

Many who reviewed the TouchPad pointed out some issues which — from what I’ve heard — have largely been addressed in the latest webOS 3.0.2 update. Now the TouchPad works a bit better, I hear, but it’s too late because the tepid reviews are already out there and sales have been disappointing. Instead of prematurely launching a half-baked tablet in a less than ideal timeframe, why not aim for a September launch of a more refined TouchPad? Fourth mistake.

I reckon this ‘bet on webOS’ has been developed like this: let’s make all the possible false steps to thwart our own products, and hope for the best. 

HP was in a unique position: the only Apple competitor to be in control of both the hardware and the software. It was a path worth risking for despite initial slow sales[1], instead HP just gave up. Without even launching the TouchPad outside of the USA. Without even trying. This, for me, is the most exasperating detail.

Now HP’s webOS VP Stephen DeWitt says that “We are not walking away from webOS” — I’m tempted to quip Well, perhaps it’s better if you just leave webOS alone instead of screwing it up even more, but really, I think that with this move, HP has shown how not serious it has been with webOS, how little it has believed in webOS, not to mention the blow to HP’s credibility as a company. How can you develop for (or buy products of) a company with this kind of throwaway approach?

 


 

  • 1. What do you expect to sell in August, anyway? I don’t know in the States, but here in Europe August is traditionally devoted to holidays — people go away, shops are closed, etc. — and is a really slow month, commercially speaking.↩

 

Ten months without Flash

Tech Life

At the beginning of November 2010, I removed Flash from all the Macs I use on a daily basis (I documented my going Flash-free here, here & here). The only exception has been the Flash plug-in inside Google Chrome, which I kept on my MacBook Pro for the occasional ‘just in case’ scenario. 

I’ve never been a fan of Flash, yet at first its removal — as opposed to using Flash-blocking tools such as ClickToFlash — seemed a bit excessive. “What if I can’t access certain content on a website because it’s in Flash?”, I thought. My fears didn’t last much, though, and not because I had left a bit of a safety net by not deleting the Flash plug-in inside Chrome. 

I don’t know whether my natural attraction to well-designed websites has always conditioned my browsing, but the fact is that I soon discovered I didn’t have one single full-Flash website in my bookmarks (well, except Typophile). And my browsing, after the Flash purge, has been even more selective. Which means, if I stumble on a Flash site, or on a site that heavily relies on Flash to deliver its contents, services, experience, without giving me any alternative (i.e. offering HTML5 contents after detecting I don’t have Flash installed), then I just browse away. Because let me tell you this: it’s 2011, and if your website still hasn’t got an HTML version to display at least its core contents, or to give me a basic idea of what it’s about, then you’re not worthy of my attention and my time.

In these ten months, I willingly opened a page with Flash contents using Google Chrome only under the following circumstances:

  1. The site, though mostly Flash-free, inexplicably featured essential parts in Flash (such as the Account Login interface);
  2. It was a Flash YouTube video I really really wanted to see (that didn’t happen very often);
  3. It was a Flash website whose link was passed on by a trusted source (read: worth seeing anyway);
  4. I wanted to access and browse Typophile.com.

Nothing else comes to mind. All in all, I very rarely felt compelled to resort to Google Chrome to enjoy something Flash-based and I never felt I was ‘missing out’ or having a somewhat crippled Web experience. The benefits of not having Flash installed (especially on older Macs) greatly outweighed the ‘drawbacks’. I put the word in quotes because, really, what drawbacks? Not being able to look at your super-cool, all-Flash, website? Or animated ads? Come on. 

(Many websites still present an irritating behaviour; they assume you’ll enjoy the Flash version more than the HTML(5) version, so they put Flash all over the place and an Enter HTML site label lost in a corner, in small typography and in such a position you’ll likely overlook the link entirely. If anything, it should be the opposite. Or better, just auto-detect the lack of Flash plug-ins in my browser and switch to HTML(5) on the fly. You’ll be amazed at the amount of sites out there that don’t perform this check.)

IBM announces the very first cognitive computing chips

Handpicked

 

From the IBM Research blog:

4. These systems won’t be programmed like traditional computers are today. Rather, cognitive computers will learn dynamically through experiences, find correlations, create hypotheses and remember – and learn from – the outcomes, emulating the human brain’s synaptic and structural plasticity (or the brain’s ability to re-wire itself over time as it learns and responds to experiences and interactions with its environment.)

5. To accomplish this new kind of system, IBM is combining neuroscience, nanoscience and supercomputing together to rival the function, power and space of the brain.

I find this stuff both incredibly fascinating and somewhat scary. With all the science-fiction literature we’ve been exposed so far, it’s hard not to imagine disquieting scenarios where the computers start being completely self-sufficient and take over the world. (But who knows, maybe they’ll manage to do a better job than us!)

See also The official IBM press release page.

Joe’s First Computer Encounter

Handpicked

The always great Lukas Mathis recently pointed to Jennifer Boriss’ blog, and it’s been a really interesting discovery. She is User Experience Designer at Mozilla Corporation and her article, User Testing in the Wild: Joe’s First Computer Encounter, was a fascinating read. It’s the account of her experience conducting a usability test with a 60-year-old man who has never used a computer.

The amount of things we tech-savvy geeks take for granted is staggering. She concludes (emphasis mine):

• There is little modern applications do to guide people who have never used a computer. Even when focusing on new users, designers tend to take for granted that users understand basic concepts such as cursors, text boxes, and buttons. And, perhaps, rightfully so – if all software could accommodate people like Joe, it would be little but instructions on how to do each new task. But, Joe was looking for a single point of help in an unfamiliar environment, and he never truly got it – not even in a Help menu

• No matter their skill level, users will try to make sense of a new situation by leveraging what they know about previous situations. Joe knew nothing about computers, so he focused on the only item he recognized: text. Icons, buttons, and interface elements Joe ignored completely

• We shouldn’t assume that new users will inquisitively try and discover how new software works by clicking buttons and trying things out. Joe found using software for the first time to be frightening and only continued at my reassurance and (sometimes) insistence. If he was on his own in an internet cafe, I think he would have given up and left after a minute or so. Giving visual feedback and help if someone is lost may help people like Joe feel they’re getting somewhere

• Don’t make too many assumptions about how users will benefit from your technology – they may surprise you!

I can confirm Boriss’ words when she writes that Joe found using software for the first time to be frightening and only continued at my reassurance and (sometimes) insistence. I’ve seen it first-hand some years ago when I helped in some computer courses for novices. The general approach of first-time computer users (especially of a certain age) was in most cases overly wary. In other words, they were constantly afraid of ‘breaking something’ or doing some kind of destructive action (not literally destructive, of course; more like “what if I make a mistake and cannot revert to a previous state?” situation). 

Another thing I noticed was that some beginners raised interface-related questions that caught me a bit off guard; exactly because, as a power user who is accustomed to computers and their interface paradigms & metaphors, I was taking for granted everything on the screen. For instance, a man asked me: “If this disk [pointing at the icon representing the boot drive] contains all this stuff in these folders [pointing at the other icons on the desktop], why is each folder as big as the disk? Shouldn’t the disk be bigger than them?”. Another user found the idea of deleting a document by dragging its icon in the Trash ‘intuitive’, but then added: “So why don’t I have to drag a document icon on a Photocopier icon to make a duplicate?”. Sure, you smile, but try to be there, answering these questions, before people who are not asking rhetorical or tongue-in-cheek questions and want straight answers right away.

I should write a full account of my experience at those courses, but meanwhile here’s the moral of the story: designing interfaces is hard. Harder than you think.

Morrick’s Digest

Tech Life

When you migrate to a new web place, you’re bound to deal with your archives sooner or later, especially if you’ve been writing online for years like me. Admittedly, my English material constitutes a smaller corpus than the Italian’s (my first official Mac-oriented blog started in 2005 and was in Italian). When I was preparing this website for launch, roughly a month ago, I considered doing a simple export-import operation from my previous blog The Quillink Observer. Both this site and that blog run on WordPress, so importing the archives should have been a pain-free process, at least in theory.

In reality, as always, things aren’t that simple. Two main problems arose:

  1. This blog has only 5 categories and a very strict group of tags (no more than a dozen), the old blog was a mess in this regard, with categories and tags implemented in a more careless fashion and being more than 80 in total. Now, importing more than 600 posts at once and then having to go through them one by one, deleting and adjusting tags & categories would have taken a huge amount of extra time — surely delaying the launch of this website of a few more weeks. Something I didn’t want.
  2. The second problem is related to internal linking (posts containing links to other posts within my blog) and images. My archive of more than 600 posts contains self-referencing links and images hosted in the free WordPress.com installation of The Quillink Observer. If I had performed a mass import of all those posts, I would have had, again, to go through them one by one, correcting the links, uploading all the images on this space then changing the links that point to them when you click to see them bigger. Another daunting, time-consuming task.

So I decided to import only the most recent articles (say, from January 2011 on), and then revisit the archives periodically and proceed with small, incremental imports — starting with English articles, since this website is meant to favour English content.

The other day I patiently imported articles I wrote between January and May 2010, and I stumbled upon a few ones you have probably missed, since 1½ years ago my blog was surely even more obscure than it is now. So here they are. My very favourites are in bold.

  1. The lameness of netbooks — Some observations in response to Jeff Atwood’s observations regarding netbooks and their place in personal computing. (17 January 2010)
  2. Who’s afraid of the iPad? — Where, by judging some reactions to the iPad’s introduction, I feel it’s 2007 all over again, and where I make some observations regarding the iPad’s potential. (2 February 2010)
  3. A wake-up call for the current state of personal computing — It seems that a lot of people, after realising the effectiveness of the iPad’s touch interface and general user experience, have started to question and discuss what’s wrong with the current state of personal computing. (5 February 2010)
  4. Synchronised writing — Or: How I Learned to Stop Worrying about Word Processors and Love Synchronisation. (17 February 2010)
  5. Magic Mouse: out with the old, in with the new — After tolerating its shortcomings for too long, a couple of days ago I decided to stop using the Mighty Mouse with my primary Mac, pass it to my faithful G4 Cube, and buy a Magic Mouse. (19 April 2010)
  6. Not so fast — Goodbye point-and-shoot cameras? Perhaps. Goodbye laptops? Not so fast. (28 April 2010)
  7. Books are bricks — important ones. — Or: Why I’m not going to renounce my library of printed books no matter how digital the future becomes. (28 May 2010)

As always, thanks for reading.