Updating into oblivion

I updated my Nokia 700 today. It’s an unlocked, unbranded phone running Symbian Belle, that was advertised as having OS updates in February and April this year—but those updates never arrived. I eventually lost patience, and made the updates using underhand and possibly illegal tools. iPhone 4 (with bumper), Galaxy Nexus, Nokia 700

In an earlier post I said that I wasn’t too bothered about OS updates. For the most part that’s true. I don’t mind that my Android tablet (the original Galaxy Tab) hasn’t had an update since Android 2.3. I appreciate that Samsung gave some sign of having actually looked into whether an update would run well on it and decided that it wouldn’t. That puts me in a better position than friends with the iPhone 3 who had their devices rendered into sludge by an iOS update too far.

But Nokia—they really worked hard at winding me up. The February update didn’t just piddle about with the core OS, it also added some applications that I was genuinely interested in trying and that couldn’t be installed any other way. The April update didn’t mess about either, it actually increased the phone’s CPU clock speed. (How? Why was it lower to begin with?)

And for UK unlocked devices, they had two product codes: evidently the good and the bad. The good got the updates, and I had the bad. The bad didn’t get the updates.

So having waited until late July, I lost patience and re-flashed the thing.

I’m a bit cross about it because of, well, being put to such lengths and made to feel like I actually cared, about something so trivial.

On the other hand… a Nokia 700 with the latest Belle FP1 is a really nice phone. It’s hard to stay cross for long.

Neat, thin form factor, excellent screen, expandable storage and replaceable battery, physical buttons all well placed. Yes, it’s immaculately built… in Hungary, where Nokia laid off most of their workers at the end of last year.

With Belle FP1 and the faster clock speed, it’s smooth, straightforward and enjoyable to use. Sure there are some extra things I could still do with (integrated notifications of new email for example) but it’s for the first time a phone I could actually recommend to friends who liked the size and construction… running on an operating system cut adrift in February last year and effectively canned with Nokia’s last round of layoffs.

There aren’t as many good apps as on other platforms, but it does have a number of smooth Qt-based ones, including a few very slick and useful apps from Nokia, and it’s an attractive device for a Qt developer like me to think of developing for… if only there was an ecosystem around it and if only future devices were compatible… and if Nokia hadn’t abandoned Qt in their platform strategy twice, once with the switch to WP7 and again when refocusing on S40 a month ago.

Yep, the 700 is a wonderful example of what might have been.

I’m tempted to buy another as a spare, just because I like it so much and its future is so plainly bleak. I wonder how many of the services on it would stop working if Nokia went under?

Windows Phone 8 and Nokia

Microsoft formally announced Windows Phone 8 yesterday.

There were some interesting technical details in the announcement: it permits running native code, will apparently support individual app distribution centres for corporate users, and has a less boring home screen.

They also confirmed, as expected, that there will be no upgrades from Windows Phone 7.

I’m not sure this will be such a big deal for existing users. I think it’s easy to overstate how much users generally care about updates, and at least this way there is certainty—in contrast to Nokia’s update mechanism for Symbian which involved announcing the update first, then rolling it out to devices over a period of months or in some cases not at all.

It can’t help the sales potential of current devices though.

What are Nokia trying to sell?

Looking at Nokia’s UK site now, it shows 24 phones (that’s down from 105 phones and a laptop, just before the February 2011 reshuffle).

Of those 24, four run the Windows Phone 7 whose non-upgradeable successor was just announced.

A further four, I think, run variants of Symbian. The most up-to-date (Belle) was recently effectively canned. But hey, only one phone ships with that anyway—the rest come with even more out-of-date variants.

The remaining 16, if I’m counting correctly, run the S40 Java-mobile feature phone platform and are presumably sold at pretty thin margins.

Nokia are I suppose hoping to have WP8 phones out by Christmas. That’ll be nearly two years after their “burning platforms” strategic reset, and they’ll be pretty much back where they started: abandoning three legacy platforms, pinning their hopes on a new one starting from zero market share. How much cash have they got left?

Nokia: “You know, we might be in a spot of bother after all”

(All over the internet for the last couple of days, but for best subhead I must link to the Register.)

Nokia 700, iPhone 4 (with bumper), Galaxy NexusBeing a contrary type, I recently bought a Nokia 700. You can see it on the top of the pile in the photo on the right.

It runs Nokia (Symbian) Belle, an unevenly-supported platform that started at a disadvantage and is now to be abandoned by a dying company. The software is not this phone’s high point, though it’s better than you’d expect from that description.

The hardware is fantastic. It’s just the right size, shape, and construction. I resisted the iPhone and friends for years because they were so clumsy, but the 700 is small and thin enough to fit in any jeans pocket while still being entirely manageable with the Swype keyboard. (There are small Android phones, but they’re all horrible.)

And it’s a more beautiful object than any other phone I’ve seen. It isn’t any nicer to hold, or more practical: there are Android and WP7 phones that are better in the hand, and the 700 has no parallel lines in its design and so is impossible to balance satisfactorily on any edge. But it has the air of a weird tablet passed to us by aliens in its thinness, lightness, solidity, and amenability to single-handed hold and operation.

What Nokia Did Back Then

The way Nokia made their mark, back when mobile phones first became popular—in the mid to late 90s—was by producing desirable hardware with a recognisable operating system.

Nokia pioneered the idea of a consistent operating system for phones. They made a series of devices all working in much the same way, at a time when others were producing new interfaces for every device, and they had a sensible and comprehensible structure for information and functions on screen.

Nokia quickly became the phone you could actually understand, while producing the desirable hardware that made them the phone you yearned to own. This is just the combination we see in Apple now, and it’s the combination that Nokia lost sight of during their years of pushing capable but complex Symbian systems.

Of course, Nokia have now managed to pull Symbian back into a position where ordinary people can enjoy it—four or five years too late.

Our Frightful Infrastructure

I had never used Symbian before buying this phone.

I had used Windows Phone 7, and I liked it. So I could see where Nokia were going and why.

I knew that the WP7 ecosystem is entirely owned by Microsoft. You get your new phone and switch it on; you’re asked to register a Windows Live account (or whatever they’re calling it now); and you’re entirely managed within Microsoft’s network of services. Music, games, video, support services, what have you: it’s all Microsoft.

What I hadn’t realised was just how much infrastructure Nokia already had around Symbian. You get your new Nokia 700 and, as soon as you try to do anything acquisitive with it, you’re asked to register a Nokia account. You use entirely Nokia services for music, games, video, support services, and what have you. And they work quite well.

As an ignorant observer, I had thought that Nokia was deferring to Microsoft in these services because they didn’t have them already. I now realise the switch to Microsoft services is simply a change of landscape. They already did have all of these things working fine.

But the way Nokia ran these services was terribly labour-intensive. Their dependency on mobile phone carriers meant they had to organise separate billing and delivery plans several times over for every region. Delivering OS updates appears to be an almost impossible task: my phone is still waiting for updates that Nokia announced, and I know that other editions of the same phone received, over four months ago.

I’ve been in touch with Nokia support several times about failed music downloads and missing OS updates, and they’ve never been able to tell me anything useful about what was really going on. The system has been creeping past its operators on both flanks.

Can Nokia recover?

No. Though everyone is saying that, so I’m hardly original.

Nokia have clearly discarded Symbian, which seems to be both expensive to run and without a place in the market. (I wonder how long the services for my lovely phone will keep running for.)

That means they have only two totally incompatible platforms to manage, instead of three: S40 running Mobile Java, and WP7 running managed .NET code.

WP7 is not going to succeed for Nokia. I like it, but not only does it look like a hard sell for consumers, it’s also an operating system that people talk about more than they talk about the phones.

What I mean by that is: Nokia are trying to sell phones with a nearly two-year-old operating system called Windows Phone 7. Delightful though it is to use, it has no very immediate appeal to consumers in terms of immediate visuals or capabilities so the publicity talks about the operating system rather than simply presenting the phones. We know that the phones are running Windows.

Meanwhile, Microsoft are already talking up Windows 8. Anyone in a position to influence reluctant consumers is probably already thinking of WP7 as a strange and not necessarily compatible predecessor of Windows 8, whatever that turns out to be. (We’ve seen a lot of Windows 8, but it’s proposed that it will run on phones as well as PCs and tablets [isn't it?], and we haven’t seen any of that yet.)

Nokia are in the awkward position of betting their entire business on explicitly promoting an operating system that seems to have been already superseded by its producers.

No, I think they’ve had it. It’s been a long time coming, but I just don’t see the way out. Let’s hope I’m wrong, because it’s terribly painful to watch a strong European company fall apart because they couldn’t understand the nature of competition from a formerly minor American rival. Damn it.

“Papermill” and paying for apps

Ryan Bateman writes an interesting piece about Papermill, an Android client for the Instapaper offline web-page reading service (via Daring Fireball).

What makes it so fascinating is the inclusion of actual numbers for both sales figures and (estimated) time spent on development. The results look rather depressing for any developer who likes the idea of providing a straightforward product and charging a reasonable price, rather than using backhanded mechanisms such as in-app sales or advertising.

One subjective point, though: I had never heard of this application, and at $4 it’s the sort of thing I might well pay for myself (as someone who does pay for Android apps).

But:

To get started all you need is an Android 2.2+ device and an Instapaper subscription account. A subscription account costs $1 a month and allows you to use third-party applications (such as Papermill) with your Instapaper account.

So to evaluate Papermill, you not only have to pay for the app, but also go and set up a subscription payment for Instapaper, which is a separate service from a different provider. And Google give you 15 minutes to get a refund if this combination doesn’t work out. (I suppose at least you can get a refund.)

I’m not really surprised that few people actually get around to doing this, no matter how little the sums involved. I think perhaps commentators are making the mistake of assuming most people have already used Instapaper.

Meanwhile in his linking article, John Gruber writes

Apple may never release a new non-high-end phone, but they do have mid-range and low-end smartphone models: the iPhone 4 and 3GS.

The 3GS costs £319 off-contract: that’s about three times what I would think of as a low-end smartphone.

Operating system updates

Google have released a version of their Chrome web browser for Android, and it seems to be rather good—but it only runs on the very latest version of Android, version 4. Which is a bit of an annoyance, because hardly anybody has that version.

Glancing at the 12 most popular Android phones on the Expansys site, I can see only two—the two variants of Google’s Galaxy Nexus—supplied with Android 4. That’ll change, but in the mean time there hasn’t been much of a rush to provide updates for older phones.

I’m generally ambivalent about operating system updates. I believe that both phones and PCs are bought on the basis of the way they look and work at the time, not in the expectation that updates will change anything significant.

As a long-term Linux user I’m all too familiar with the concept of the Ubuntu update that breaks everything, but I think my uncertainty about the wisdom of updates is common among people using most kinds of computer.

I updated my Galaxy Tab from Android 2.2 to 2.3: it improved battery life a bit, stopped cut and paste working in some applications, and provided no obvious interface improvements—not a big net positive. I know iPhone users who complain about Apple persuading them to install updates that slow down their previously perfectly good phones. My wife updated her WP7 phone recently, grumbling about the amount of time and laptop disc space used by the installer, only to find the update made no detectable change at all. OS/X 10.7 had a decidedly mixed response from users of earlier versions.

Why would anyone want to update anyway?

What drives updates is application support. The only time most users will start hunting for an operating system update—as opposed to installing one that’s thrust into their face by the device itself—is when they find they can’t run applications they care about because their OS is too old.

Even then, they’ll probably resent having to update to do it.

I don’t really care about Android 4 on my own device, which is fortunate because it doesn’t appear to be available. But I would like to try out Chrome. (There are several OK browsers for Android, but no really good ones—and the one I like best in principle, Firefox, itself gets less stable for me with every update.)

I wonder how fundamental Chrome’s dependency on Android 4 really is. Perhaps the only reason it didn’t exist before was that it needed some quite basic OS support that earlier versions couldn’t provide.

Or perhaps the dependency is seen as a serendipitous one, and the release of Chrome as a way to encourage users like me, and phone manufacturers, to update as soon as possible.

Buy Our Superior Celluloid Cylinders

M., brandishing new telephone: I find it a bit difficult to actually make phone calls, but it’s great for the internet. No, I really like it. The battery’s hopeless though.

Me: How often do you have to charge it?

M.: About every two days. I thought it was defective at first.

A fun mental exercise is to think of an old product that has been superseded by a newer one, and imagine that their roles are reversed—would you be able to sell anyone the old product as a replacement for the new?

VHS tapes, for example: more intuitive seeking than your old DVD player; no unskippable gubbins at the start; the tape remembers where you’d got up to if you stop and restart; easy to record and re-record on. Very practical!

Awful picture and sound quality though, and much too big. Probably wouldn’t sell all that many, but you’ve at least got the beginnings of a promotional campaign there. You could have a crack at it.

Similarly, DVD looks pretty promising as an improvement over Blu-Ray, being superior in almost every practical detail.

I can imagine trying to flog LP records as an alternative format to digital audio, with quite distinct areas of strength, though I can’t see all that much hope for CDs in between.

Selling your “All-New Feature Phone” as a low-cost, lightweight, miniaturised upgrade for a smartphone would be tricky. Popular new technologies often involve new input methods, and users find it very hard to go back. But if you had to try, you could make a pretty good start by talking about batteries.

Imagine being able to go on holiday for a week or more, and still stay in touch without having to ever worry about finding a charger. That’s what the latest battery management technology exclusive to “Feature Phones” brings you!

The original iPhone reintroduced the sort of comically short battery life familiar to those of us who had mobile phones in 1997 or thereabouts, and since then phones seem to have been going about the same way as laptops did during the 2000s—a series of incremental improvements consumed by incrementally more powerful hardware, meaning we ended the decade with much the same order of magnitude of battery life as we started with.