Apple's iOS 7 isn't for you. But you should upgrade anyway

The secret target of Apple's new iOS releases is developers. But that doesn't mean users don't get benefits.

There's been a pattern with recent versions of iOS, the operating system which runs iPhones and iPads (and iPod Touches, the forgotten bottom rung of Apple's mobile strategy). Users see shiny new features, and upgrade in a rush. Then, after a few weeks of having fun with them, they find that the underlying problems they had with the operating system haven't really gone away, and that the vast majority of the features are more like gimmicks than actual improvements. Increasingly often, the ones which actually do offer something new and useful are done better by a third-party app: that's true of Safari's reading list (try Instapaper or Pocket instead) and of iCloud's… well, everything. (Dropbox offers the same feature set but has a better habit of actually working).

With iOS 7, due to hit on September 10, the "shiny" part of "shiny new features" takes the foreground. The new design has it's fair share of detractors, but if there's one thing it offers in spades, it's the veneer of newness. As a way to make an old phone feel fresh, even for just a couple of weeks, a new UI is perfect. But, of course, it's unlikely to change any problems you have with what your phone does today.

Here's the thing, though: iOS 7 isn't for you. Not really. So it doesn't matter if you get bored within a week of upgrading, so long as you do in fact upgrade. Because Apple needs a lot of users on the latest version of iOS to justify it to developers, the real targets of the new OS.

Every major upgrade of iOS has included a lot of consumer facing features, some more essential than others. But they've also included far more hooks for developers to use when they're making. That goes right back to iPhone OS 2, which introduced the App Store in the first place (in hindsight perhaps the most important software update of the last decade). But even since then, the changes have been relatively major. iPhone OS 3 introduced Core Data, a framework for managing databases; iOS 4 added features letting programmers more easily optimise for multiple processors; iOS 5 added image processing technology; iOS 6 upgraded the application programming interface (API) for dealing with cameras, maps and Facebook.

As well as those changes, there's the same low-grade improvements behind the scenes as there are up front. All of which means that, if you're making an app for the iPhone, it's a lot more pleasant to only have to support the latest version of two of iOS, rather than try and keep up complete backwards compatibility. But the flip-side of only supporting the latest versions is that you lose potential customers, as everyone who hasn't got round to upgrading is locked out.

And that's where the bells and whistles come in. With the new features in every version of iOS, and the effort put into making them backwards compatible with older phones (something which has no immediate payoff, and could even reduce the number of people upgrading to the latest model on release day), Apple manages to ensure that an astonishingly high percentage of customers are on the latest version. Ninety-four per cent of its customers are using iOS 6, and another 5 per cent are on iOS 5. Compare that to Android, where backwards compatibility is often limited (and carriers stand in the way of upgrades): 33 per cent of users are on Gingerbread, a release which came out over two and a half years ago. The latest version of Jelly Bean, which was released in July this year, has been adopted by so few that, as of August 1, Google wasn't even reporting numbers. The version before, released in November 2012, has just 6.5 per cent take up. It is only two months newer than iOS 6.

That coherence of the user base is a large part of the reason why iOS is considered preferable to develop for by many programmers (other reasons include iOS users increased tendency to spend money on things, and developers wanting to make apps for the phones they use); and that is why, despite Android having a far higher share of total smartphone users, iOS continues to get many large apps first or even exclusively.

So even though iOS 7 isn't for you, you'll get its benefit eventually. Just wait and look at the pretty colours in the meantime.

An iPhone running iOS 7. Photograph: Getty Images

Alex Hern is a technology reporter for the Guardian. He was formerly staff writer at the New Statesman. You should follow Alex on Twitter.

Show Hide image

Geoffrey Howe dies, aged 88

Howe was Margaret Thatcher's longest serving Cabinet minister – and the man credited with precipitating her downfall.

The former Conservative chancellor Lord Howe, a key figure in the Thatcher government, has died of a suspected heart attack, his family has said. He was 88.

Geoffrey Howe was the longest-serving member of Margaret Thatcher's Cabinet, playing a key role in both her government and her downfall. Born in Port Talbot in 1926, he began his career as a lawyer, and was first elected to parliament in 1964, but lost his seat just 18 months later.

Returning as MP for Reigate in the Conservative election victory of 1970, he served in the government of Edward Heath, first as Solicitor General for England & Wales, then as a Minister of State for Trade. When Margaret Thatcher became opposition leader in 1975, she named Howe as her shadow chancellor.

He retained this brief when the party returned to government in 1979. In the controversial budget of 1981, he outlined a radical monetarist programme, abandoning then-mainstream economic thinking by attempting to rapidly tackle the deficit at a time of recession and unemployment. Following the 1983 election, he was appointed as foreign secretary, in which post he negotiated the return of Hong Kong to China.

In 1989, Thatcher demoted Howe to the position of leader of the house and deputy prime minister. And on 1 November 1990, following disagreements over Britain's relationship with Europe, he resigned from the Cabinet altogether. 

Twelve days later, in a powerful speech explaining his resignation, he attacked the prime minister's attitude to Brussels, and called on his former colleagues to "consider their own response to the tragic conflict of loyalties with which I have myself wrestled for perhaps too long".

Labour Chancellor Denis Healey once described an attack from Howe as "like being savaged by a dead sheep" - but his resignation speech is widely credited for triggering the process that led to Thatcher's downfall. Nine days later, her premiership was over.

Howe retired from the Commons in 1992, and was made a life peer as Baron Howe of Aberavon. He later said that his resignation speech "was not intended as a challenge, it was intended as a way of summarising the importance of Europe". 

Nonetheless, he added: "I am sure that, without [Thatcher's] resignation, we would not have won the 1992 election... If there had been a Labour government from 1992 onwards, New Labour would never have been born."

Jonn Elledge is the editor of the New Statesman's sister site CityMetric. He is on Twitter, far too much, as @JonnElledge.