Tag Archives: mobile

RIM hints at move to license BlackBerry 10 OS to third parties

RIM chief Thorsten Heins says in an interview that his company may license the forthcoming BlackBerry 10 mobile operating system to third parties. Here is the key quote:

We don’t have the economy of scale to compete against the guys who crank out 60 handsets a year. We have to differentiate and have a focused platform. To deliver BB10 we may need to look at licensing it to someone who can do this at a way better cost proposition than I can do it. There’s different options we could do that we’re currently investigating.

He goes on to talk about:

… us building a reference system, and then basically licensing that reference design, have others build the hardware around it – either it’s a BlackBerry or it’s something else being built on the BlackBerry platform

The big question: would the likes of Samsung and Sony leap to manufacture BlackBerry OS smartphones when they can offer Android for free?

A more nuanced question: even if OEMs were to license BlackBerry OS, to what extent would they really get behind it, as opposed to cranking out a few devices to see how they went? The latter is what happened to Windows Phone 7, with the exception of Nokia late in the day.

Samsung manufactures Windows Phone 7 devices, but you would hardly know it, since it is the Android-based Galaxy range that gets all its attention.

Another problem for RIM is negotiating the tricky waters of both manufacturing devices and licensing the OS to others. Apple did not enjoy having third-party manufacturers like Power Computing, Radius and Motorola release Mac clones. Here is what Walter Isaacson writes in his biography of Steve Jobs:

Apple got an $80 fee for each computer sold, but instead of expanding the market, the cloners cannibalized the sales of Apple’s own high-end computers on which it made up to $500 in profit.

Microsoft is now coming at this from the opposite end, going into hardware manufacturing with the Surface, which is another interesting experiment.

Still, listen carefully to what Heins is saying. “We don’t have the economy of scale to compete against the guys who crank out 60 handsets a year.” It is not just a matter of coming up with a fantastic mobile operating system or even a fantastic device; it is all about ecosystem, as Nokia boss Stephen Elop stated 18 months ago. RIM’s ecosystem is in decline, and the company will explore every avenue in trying to turn that around.

Internet hotspot tethering comes to the Lumia 800

Nokia’s first Windows Phone, the Lumia 800, has gained Internet Sharing in a recent update.

image

This is a fantastically useful feature if you have a data plan that includes a reasonable amount of data transfer. For example, perhaps you bought one of Google’s great value Nexus 7 tablets, reviewed here. This is Wi-Fi only, but combine it with a smartphone hotspot like this one and you can be online anywhere.

One snag is that the Lumia already has short battery life and this will drain it even faster, if enabled. If I am stuck in an airport and can find a mains point, one workaround I use is to attach the phone to a laptop via USB so that it continues to charge while you are online.

This feature removes what was to me the biggest flaw in the Lumia 800, which is an excellent phone. Unfortunately too many customers have had technical problems, the worst of which is the will not charge bug that is one of the most-read posts on this site. I have not experienced this myself for a while, so there is hope that Nokia has fixed this one too.

PhoneGap 2.0 released with WebView, Windows Phone support

Adobe has released PhoneGap 2.0, its framework for creating cross-platform mobile apps using HTML and JavaScript. Using PhoneGap, you can wrap a web application as a native app, taking advantage of the browser control available in all the major mobile platforms.

New features in PhoneGap 2.0 include Windows Phone support, WebView which lets you embed a PhoneGap fragment into a larger native application, improved tooling and a unified JavaScript API across all platforms called Cordova-JS.

The Mac tooling has been improved and no longer depends on Xcode templates. Instead, you create a new project at the command line. However, you do need Lion or Mountain Lion to use PhoneGap.

The associated Apache Cordova project is “nearing graduation from incubation”, according to Adobe’s release.

image

Microsoft financials: still growing in the cloud era, but watch out for tablets

I am in the habit of putting Microsoft’s results into a simple table. Here are the latest:

Quarter ending June 30th 2012 vs quarter ending June 30th 2011, $millions

Segment Revenue Change Profit Change
Client (Windows + Live) 4145 -598 2397 -511
Server and Tools 5092 +568 2095 +409
Online 735 +55 -6672 -5927
Business (Office) 6291 +339 4100 +399
Entertainment and devices 1779 +292 -263 -276

It is easy to spot the stars: Server and Office.

It is also easy to spot the weaklings, especially Online, which reported a breathtaking loss thanks to what the accounts call a “goodwill impairment charge”. This translates to an admission that the 2007 acquisition of aQuantive was a complete waste of money.

Mixed signals from Entertainment and devices, where revenue is up but a loss is reported. Since this segment munges together Xbox and Windows Phone, it seems plausible that the phone is the main culprit here. Microsoft identifies payments made to Nokia and the addition of Skype as factors.

Windows is down, in part because Microsoft’s upgrade offer for Windows 8 means some revenue is deferred, though one would imagine that worldwide reports of stagnant PC sales are a contributory factor as well.

If you add up the figures, and allow for overheads, it comes to a wafer-thin operating income of $192 million and a $0.06 loss per share.

What do the figures tell us? Two things: Microsoft still makes a ton of money, and that it is exceedingly bad at acquisitions. I am not sure how a company can mislay $6.2bn without heads rolling somewhere, but that is not my area of expertise.

Microsoft’s Server 2012 family has impressed me so my instinct is that we will see good figures continue there.

On the Office side, it is not all Word and Excel. “Exchange, SharePoint and Lync together grew double-digits,” Microsoft said in its earnings call, adding that Lync revenue is up 45%.

That said, how many server licences can you sell in the cloud era? How can Microsoft grow Azure without cannibalising its server sales?

It is tempting to state, like James Governor at Redmonk, that this is The End of Software: Microsoft Posts a Loss for the First Time ever. Microsoft’s figures have stubbornly refused to prove this though; and a quarter where revenue has risen though poisoned by an acquisition disaster is not the moment to call it.

Microsoft has survived the cloud. The bigger question now is whether it can also survive tablets eating into its Windows sales, not helped by Google pushing out Nexus 7 at casual purchase price – see my first take here.

All eyes then on the new Windows 8 and Office 2013.

Microsoft to make its own tablet called Surface, puts Windows RT centre stage

Microsoft has announced its own tablet, called Surface, for “work and play”, said CEO Steve Ballmer at an event in Los Angeles yesterday.

image

The first of what will be a family of devices has a 10.6” Corning Gorilla Glass screen, is just 9.3mm thick, and has a magnesium “VaporMg” case with a built-in stand/magnetic cover which doubles as a multitouch keyboard.

Surface comes in two forms. One runs Windows RT with an NVidia processor, which means it is the ARM version of Windows 8. There is a desktop UI alongside Metro, but the desktop is there only to run Microsoft Office (which is bundled), Explorer, and whatever other utilities Microsoft chooses to include. It is not possible to install new desktop applications. Users can only install Metro-style apps from the Windows Store.

The other runs Windows 8 Professional. Note that this x86 version is heavier (903g vs 676g), thicker (13.5mm vs 9.3mm) and more power-hungry (42 W-h vs 31.5 W-h). However, it does benefit from USB 3.0 rather than USB 2.0.

Why has Microsoft done this, and risked alienating the hardware partners on which it depends for the success of Windows?

I posted on this subject a few days ago. Yes, Microsoft’s hardware partners have driven the success of Windows, but they have also been part of the problem as Apple has captured a gradually increasing proportion of the personal computer market. Problems include foistware(unwanted software) bundled with PCs and rushed designs that have too many annoyances.

With Windows Phone 7, it was not until Nokia entered the market a year after the launch that we saw hardware and design quality that does justice to the operating system. Distracted by Android, partners like HTC and Samsung brought out drab, unimaginative phones that contributed to a poor start for Microsoft’s smartphone OS.

Now with Windows 8, the danger is that the same may happen again. We have seen few Windows RT designs, and evidence that vendors are having difficulty in reimagining Windows.

Until today, that is. The announcement ensures that Windows RT will win plenty of attention at launch, alongside the x86 editions, and that Microsoft has a measure of control over its own destiny, in how Windows 8 is realised in hardware.

Microsoft says that the Windows RT Surface will launch at the same time as Windows 8, but that the Intel edition will follow a few months later.

How much for a Surface? The press release says:

Suggested retail pricing will be announced closer to availability and is expected to be competitive with a comparable ARM tablet or Intel Ultrabook-class PC. OEMs will have cost and feature parity on Windows 8 and Windows RT.

image

Microsoft, Windows 8, and the Innovator’s Dilemma (or, why you hate Windows 8)

One thing is obvious from the immediate reaction to Windows 8 Release Preview. Most of those who try it do not like it. It is a contrast to the pre-release days of Windows 7, when there was near-consensus that, whatever you think of Windows overall, the new edition was better than its predecessors.

Why would a company with huge resources and the world’s most popular desktop operating system – 600 million Windows 7 licenses so far, according to OEM VP Steven Guggenheimer – create a new edition which its customers do not want?

Microsoft under Steve Ballmer is a somewhat dysfunctional company – too many meetings, says ex-softie Brandon Watson – but there is still a wealth of talent there. Specifically, Windows President Steven Sinofsky has proven his ability, first with Microsoft Office 2007 which beat off the challenge from OpenOffice.org, and next with Windows 7, which if it repeated the disappointment of Windows Vista would have damaged the company severely.

If it is not incompetence, then, what is it?

In this context, Clayton M. Christensen’s 1997 classic The Innovator’s Dilemma – When new technologies cause great firms to fail is a good read. Chapter one is here. Christensen studied the hard drive market, asking why sixteen of the seventeen companies which dominated the industry in 1976 had failed or been acquired by 1995, replaced by new entrants to the market. Christensen argues that these firms failed because they listened too much to their customers. He says that delivering what your customers want is mostly a good idea, but occasionally fatal:

This is one of the innovator’s dilemmas: Blindly following the maxim that good managers should keep close to their customers can sometimes be a fatal mistake.

Specifically, hard drive companies failed because new entrants had physically smaller hard drives that were more popular. The reason the established companies failed was because their customers had told them that physically smaller drives was not what they wanted:

Why were the leading drive makers unable to launch 8-inch drives until it was too late? Clearly, they were technologically capable of producing these drives. Their failure resulted from delay in making the strategic commitment to enter the emerging market in which the 8-inch drives initially could be sold. Interviews with marketing and engineering executives close to these companies suggest that the established 14-inch drive manufacturers were held captive by customers. Mainframe computer manufacturers did not need an 8-inch drive. In fact, they explicitly did not want it: they wanted drives with increased capacity at a lower cost per megabyte. The 14-inch drive manufacturers were listening and responding to their established customers. And their customers–in a way that was not apparent to either the disk drive manufacturers or their computer-making customers–were pulling them along a trajectory of 22 percent capacity growth in a 14-inch platform that would ultimately prove fatal.

Are there any parallels with what is happening in computer operating systems today? I think there are. It is not exact, given that tablet pioneer Apple cannot be described as a new entrant, though Google with Android is a closer match. Nevertheless, there is a new kind of operating system based on mobility, touch control, long battery life, secure store-delivered apps, and cloud connectivity, which is eating into the market share for Windows. Further, it seems to me that for Microsoft to do the kind of new Windows that its customers are asking for, which Christensen calls a “sustaining innovation”, like Windows 7 but faster, more reliable, more secure, and with new features that make it easier to use and more capable, would be a trajectory of death. Existing customers would praise it and be more likely to upgrade, but it would do nothing to stem the market share bleed to Apple iPad and the like. Nor would it advance Microsoft’s position in smartphones.

Should Microsoft have adapted its Windows Phone OS for tablets two years ago, or created Metro-style Windows as an independent OS while maintaining Windows desktop separately? YES say customers infuriated by the full-screen Start menu. Yet, the dismal sales for Windows Phone show how difficult it is to enter a market where competitors are firmly entrenched. Would not the same apply to Windows Metro? Reviewers might like it, developers might like it, but in the shops customers would still prefer the safety of iPad and Android and their vast range of available apps.

You begin to see the remorseless logic behind Windows 8, which binds new and old so tightly that you cannot escape either. Don’t like it? Stick with Windows 7.

Microsoft will not say this, but my guess is that customer dissatisfaction with Windows 8 is expected. It is the cost, a heavy cost, of the fight to be a part of the next generation of client computers. It is noticeable though that while the feedback from users is mostly hostile, Microsoft’s OEM partners are right behind it. They do not like seeing their business munched by Apple.

The above does not prove that Microsoft is doing the right thing. Displeasing your customers, remember, is mostly the wrong thing to do. Windows 8 may fail, and Microsoft, already a company with shrinking influence, may go into an unstoppable decline. Bill Gates was right about the tablet taking over from the laptop, history may say, but Microsoft was incapable of making the radical changes to Windows that would make it work until it was too late.

Give credit for this though: Windows 8 is a bold move, and unlike the Tablet PCs that Gates waved around ten years ago, it is an OS that is fit for purpose. Sinofsky’s goal is to unify the smartphone and the tablet, making a new mobile OS that users will enjoy while also maintaining the legacy desktop and slotting in to enterprise management infrastructure. I admire his tenacity in the face of intense protest, and I am beginning to understand that foresight rather than stupidity underlies his efforts.

Review: Digital Wars by Charles Arthur

Subtitled Apple, Google, Microsoft and the battle for the internet, this is an account by the Guardian’s Technology Editor of the progress of three tech titans between 1998 and the present day. In 1998, Google was just getting started, Apple was at the beginning of its recovery under the returning CEO Steve Jobs, and Microsoft dominated PCs and was busy crushing Netscape.

Here is how the market capitalization of the three changed between 1998 and 2011:

  End 1998 Mid 2011
Apple $5.4 billion $346.7 billion
Google $10 million $185.1 billion
Microsoft $344.6 billion $214.3 billion

This book tells the story behind that dramatic change in fortunes. It is a great read, written in a concise, clear and engaging style, and informed by the author’s close observation of the technology industry over that period.

That said, it is Apple that gets the best quality coverage here, not only because it is the biggest winner, but also because it is the company for which Arthur feels most affinity. When it comes to Microsoft the book focuses mainly on the company’s big failures in search, digital music and smartphones, but although these failures are well described, the question of why it has performed so badly is not fully articulated, though there is reference to the impact of antitrust legislation and an unflattering portrayal of CEO Steve Ballmer. The inner workings of Google are even less visible and if your main interest is the ascent of Google you should look elsewhere.

Leaving aside Google then, describing the success of Apple alongside Microsoft’s colossal blunders makes compelling reading. Arthur is perhaps a little unfair to Microsoft, because he skips over some of the company’s better moments, such as the success of Windows 7 and Windows Server, or even the Xbox 360, though he would argue I think that those successes are peripheral to his theme which is internet and mobile.

The heart of the book is in chapters four, on digital music, and five, on smartphones. The iPod, after all, was the forerunner of the Apple iPhone, and the iPhone was the forerunner of the iPad. Microsoft’s famous ecosystem of third-party hardware partners failed to compete with the Ipod, and by the time the company got it mostly right by abandoning its partners and creating the Zune, it was too late.

The smartphone story played out even worse for Microsoft, given that this was a market where it already had significant presence with Windows Mobile. Arthur describes the launch of the iPhone, and then recounts how Microsoft acquired a great mobile phone team with a company called Danger, and proceeded to destroy it. The Danger/Pink episode shows more than any other how broken is Microsoft’s management and mobile strategy. Danger was acquired in February 2008. There was then, Arthur describes, an internal battle between the Windows Mobile team and the Danger team, won by the Windows Mobile team under Andy Lees, and resulting in 18 months delay while the Danger operating system was rewritten to use Windows CE. By the time the first new “Project Pink” phone was delivered it was short on features and no longer wanted by Verizon, the partner operator. The “Kin” phone was on the market for only 48 days.

The Kin story was dysfunctional Microsoft at its worst, a huge waste of money and effort, and could have broken a smaller company. Microsoft shrugged it off, showing that its Windows and Office cash cows continue to insulate it against incompetence, probably too much for its own long-tem health.

Finally, the book leaves the reader wondering how the story continues. Arthur gets the significance of the iPad in business:

Cook would reel off statistics about the number of Fortune 500 companies ‘testing or deploying’ iPads, of banks and brokers that were trying it, and of serious apps being written for it. Apple was going, ever so quietly, after the business computing market – the one that had belonged for years to Microsoft.

Since he wrote those words that trend has increased, forming a large part of what is called Bring Your Own Device or The Consumerization of IT. Microsoft does have what it hopes is an answer, which is Windows 8, under a team led by the same Steven Sinofsky who made a success of Windows 7. The task is more challenging this time round though: Windows 7 was an improved version of Windows Vista, whereas Windows 8 is a radical new departure, at least in respect of its Metro user interface which is for the Tablet market. If Windows 8 fares as badly against the iPad as Plays for Sure fared against the iPod, then expect further decline in Microsoft’s market value.

 

Nokia Lumia strategy needs time, may not have it

A quick comment on Nokia’s dismal results for the first quarter of 2012. Sales are down 26% quarter on quarter; Smartphone sales down 38% despite the introduction of the Lumia Windows Phone in Europe. Negative operating margin, heavy losses.

The reasons given?

  • competitive industry dynamics continuing to negatively affect the Smart Devices and Mobile
    Phones business units;
  • timing, ramp-up, and consumer demand related to new products; and
  • the macroeconomic environment.

Translation: the new Lumias are failing to compete effectively against Apple iPhone and Google Android devices.

I have a Lumia 800 and like it increasingly. It is elegant and nice to hold, it works well, and Nokia Drive makes an excellent SatNav, to mention three good things.

image

Nevertheless, I am not surprised by the poor sales. When I first got the Lumia its battery life was poor; it is still not great, but was much improved by the last firmware update I installed (1600.2487.8107.12070), for which I had to use a manual process.

There was also an aggravating problem where if the phone ran out of power completely, it could not easily be charged. In other words, it was nearly a brick, though I managed to coax it back to life by repeatedly reconnecting the charger. The problem seems to be fixed with the latest update.

I do not think my experience is untypical, and can see that while in one sense it is a great phone, from another perspective it qualifies as buggy and problematic; I expect returns were above average.

The problems are fixable, but with hindsight Nokia should have worked that bit harder to ensure a trouble-free launch. The US launch of the Lumia 900 may be better since the company has had a little more time to improve quality, though there was a data connection bug.

Everything to prove

The bigger problem is that Windows Phone has everything to prove; iPhone and Android dominate the market, so the Lumia has to be sufficiently better to win customers over to a braver choice.

App availability is another factor. Windows Phone is not on the radar for most app vendors – because its market share is too small.

Despite a few lapses, I have been impressed with what I have seen of Nokia’s Windows Phone efforts. Nokia’s marketing and developer evangelism has been far better than Microsoft’s. At Mobile World Congress in February Microsoft had a large stand but was mainly doing silly “smoked by Windows Phone” demos, while Nokia’s stand was humming with activity.

Microsoft more to blame than Nokia

I also incline to the view that Microsoft is more to blame than Nokia – except insofar as Nokia could have made a different choice of partner.

Windows Phone 7 was nicely designed but badly launched, more than a year before the Lumia appeared. The launch hardware was uninteresting and Microsoft failed to line up strong operator or retail support for its devices. Microsoft focused on quantity rather than quality in the Windows Phone app store, resulting in a mountain of rubbish there.

The pace of development in the Windows Phone 7 operating system has also been rather slow, but the issues are more to do with marketing and partner support than with the OS itself.

Nokia has gone some way towards fixing the issues. Its devices are better, and so is its marketing. It is unlikely though that Nokia can succeed unless Microsoft also ups its smartphone game.

The future

Microsoft’s strategy for Windows Phone and Windows 8, as far as I am aware, does make some sense. We will see convergence of the operating system, improved tool support with an option for native code development, and a coherent cloud story.

This will take time to unfold though. It also seems likely that Windows 8 will have a rocky launch, with desktop users disliking the Metro-style elements imposed for the sake of tablet support. Nokia has indicated that it will be producing Windows 8 tablets as well as phones, but whether this will be an instant hit is at the moment uncertain.

Who knows, perhaps it will be Windows 9 before Microsoft really makes its tablet strategy work.

The problem is that Nokia does not have time to wait while Microsoft sorts out its mobile phone and tablet strategy. It needs quick success.

Two final thoughts.

First, Microsoft can hardly afford to see Nokia fail, so some sort of acquisition would not surprise me.

Second, how difficult would it be for Nokia to bring out some Android smartphones alongside its Windows range? Currently we are told that there is no plan B, but perhaps there should be.

Apple breaks web storage in iOS 5.1, does not care about web apps?

Many iOS apps which rely on web storage APIs for persistent data have been broken by the recent upgrade to iOS 5.1. The issue affects apps built with PhoneGap or others which use WebKit APIs to store data. The affect for users is that they lose all their data after the upgrade. For example, it sounds like the issue has hit this app:

image

Another developer says:

My statistics show users abandoning ship as their settings are wiped over and over, after each app restart.
This is a critical error that must be patched as soon as possible. Remember there’s also a delay from Apples app approval process to consider.

Put more precisely, WebKit used to store its local databases in Library/WebKit which is a location that the OS regards as persistent and which is backed up to iCloud. In iOS 5.1 this data is stored in Library/Caches which means it is regarded as temporary and likely to be deleted. The W3C Candidate Recommendation says of localStorage:

User agents should expire data from the local storage areas only for security reasons or when requested to do so by the user.

An embedded browser is not quite the same as a web browser though, and if you are using SQLite in Webkit then that falls outside the W3C HTML 5 API since Web SQL is no longer included.

The issue is complicated in that there also seems to be a bug, described here, which causes data to be lost after upgrading an app to a newer version; and there are problems with actual web apps as well as with apps that use an embedded UIWebView.

PhoneGap is fixable in that it can call native APIs and there is work going on to implement this. The danger is that more platform-specific code undermines the cross-platform benefits.

Discussions on the Apple developer forums during the beta period for 1OS 5.1 show that Apple was aware of the issue and that it is by design. The impression given is that Apple was annoyed by the number of apps using web storage to speed up their apps (whether web or native) rather than just storing customer-created content, and felt it was imposing too much burden on the constrained storage space in an iOS device.

It does not help that there is no way to increase the storage in an iPad or iPhone other than by replacing it with a newer one with more memory.

The problem is a real one, but you cannot escape the impression that Apple considers solutions like PhoneGap, or even web apps that behave like local apps, as a kind of workaround or hack that is to be discouraged in favour of apps written entirely with the iOS SDK.

Apple benefits from true native apps as they are more likely to be exclusive to its platform, and must be sold through the App Store with a fee to Apple.

The official Data Storage Guidelines for iOS are here.

Sold out QCon kicks off in London: big data, mobile, cloud, HTML 5

QCon London has just started in London, and I’m interested to see that it is both bigger than last year and also sold out. I should not be surprised, because it is usually the best conference I attend all year, being vendor-neutral (though with an Agile bias), wide-ranging and always thought-provoking.

image

A few more observations. One reason I attend is to watch industry trends, which are meaningful here because the agenda is driven by what currently concerns developers and software architects. Interesting then to see an entire track on cross-platform mobile, though one that is largely focused on HTML 5. In fact, mobile and cloud between them dominate here, with other tracks covering cloud architecture, big data, highly available systems, platform as a service, HTML 5 and JavaScript and more.

I also noticed that Abobe’s Christophe Coenraets is here this year as he was in 2011 – only this year he is talking not about Flex or AIR, but HTML, JavaScript and PhoneGap.