30 Comments

Summary:

One would think that owning the largest smartphone market share in the world ought to attract the most high-quality mobile software developers developers, but doesn’t seem to the case for Nokia. Too many products on too many permutations of platforms and a sub-par store aren’t helping.

UPDATED: One would think that laying claim to the largest share of the world’s smartphone market would attract the most high-quality mobile software developers, but that doesn’t seem to the case for Nokia. The Finnish phone giant’s market share stands at 44.3 percent, research firm Gartner’s latest data shows, yet according to a recent Bloomberg piece, programmers appear intent on building apps for smaller, competing platforms.

Update: Nokia Wednesday morning released an amended outlook that further reduces expectations, with anticipated net sales in its Devices and Services division seen “at the lower end of, or slightly below” the prior expected range of 6.7-7.2 billion euros in the second quarter of 2010. Nokia attributes the new forecast to “the competitive environment, particularly at the high-end of the market, and shifts in product mix towards somewhat lower gross margin products.” In other words, Nokia sees its struggle in the thriving market for smartphones and the software they run.

The challenge Nokia has faced and will continue to face can be boiled down to three things:

Negative momentum: Commenters are always quick to remind me of Nokia’s No. 1 position in terms of smartphone market share, and rightly so. But such numbers are a snapshot in time — far more important to developers is momentum. They watch to see how fast or slow a platform is gaining or losing acceptance. In the case of Nokia, there’s been momentum over the past three years, just not the good kind. Our infographic on mobile platform share from 2007-2009 highlights the problem — Nokia’s share of the market has waned (as did Microsoft’s and general Linux phones) as those of Research In Motion , Apple and Google have grown. In other words, developers see negative momentum with Nokia and are more likely to dedicate limited resources to its platform.

Too much choice: Nokia offers more makes and models of phones than any other company. But while customer choice is important, perhaps Nokia has honed this feature to a fault. On the site for Nokia Europe — a region that the company is very strong in — there are seven N-series devices, eight E-series handsets, the unique N900 and a few more smartphones coming soon. It reminds of the current Google Android fragmentation issues, but far worse. The various Nokia smartphones all run Symbian S60 — except for the N900, which runs on Maemo — in no less than four combinations of various editions and feature packs. And then there’s the upcoming Symbian 3 OS for the Nokia N8, which is already drawing early criticism on the software and experience. What platform version should a developer target and for how long should he or she expect compatibility? Nokia’s saving grace could be the Qt cross-platform framework, but I haven’t heard any chatter about mobile developers moving to Qt in significant numbers just yet.

Poor store usability: Nokia’s Ovi store is slowly improving, but the experience isn’t up to par with that of Apple’s; even Google’s Android Market is better. A poor in-store experience doesn’t lead to sales, even if the software itself is excellent. Indeed, some developers tell Bloomberg that Nokia’s Ovi store is “clunky,” so I can’t blame such developers for leaning towards a more effective alternative storefront such as that of Apple.

The shame of it all is that Nokia makes some of the best hardware in the world when it comes to smartphones. For example, the N900 is a high-powered handset with full QWERTY keyboard and resistive touchscreen that behaves more like a capacitive display. But the Maemo operating system is geekier than Android, to the point that it initially required users to find and connect to software repositories for programs, just like a traditional Linux computer. And Maemo is going away sooner rather than later — the overall platform is now folded into the MeeGo system that Nokia merged with Intel’s Moblin, although the open source community still adds to it. Like a few other Nokia experiments, the N900 doesn’t have much of a future when compared to mainstream smartphones that are standardized on a single operating system.

Given the above three points, it’s understandable why longtime Nokia developers are moving on to greener pastures. Alan Masarek, CEO of Quickoffice, enjoys the fact that his company’s product ships on all Nokia Symbian phones, but he looked into Android about 18 months ago and is glad he did. Masarek tells Bloomberg: “The numbers on Android are very ascendant right now. We’re on all these devices that just started shipping in meaningful volumes the last two quarters.”

If Nokia can woo developers by honing its product platform and line, it can still reverse that momentum. And maybe then it can stave off a further rise in the smartphone market share of Apple and Google.

Related research report from GigaOM Pro (sub req’d):

The App Developer’s Guide to Choosing a Mobile Platform

This article also appeared on BusinessWeek.com

  1. From my personal experience, their developers tools are pretty bad too. I tried one day trying to run them properly and then got frustrated and moved to android. Even samsung bada’s tools were better than nokia.

    Share
  2. I’ve done some development for work purposes on Symbian and will not voluntarily develop for it simply because the development process and tool chain are a pain in the butt to use. I like the company and even some of the phones, but have given up on using it for personal or professional pursuits for now.

    Share
  3. You missed out on the biggest point, while Nokia has the largest phone share, it has a small smartphone share. This is where the money is at for developers.

    Share
    1. A small smartphone share? It’s actually 40%.

      Silly comment is silly.

      Share
    2. cak, you missed out on the first sentence. ;)

      “One would think that laying claim to the largest share of the world’s smartphone market would attract the most high-quality mobile software developers….”

      Share
      1. One of Nokia’s problems is that the definition of “smartphone” has shifted out from under the products Nokia sells.

        The modern smartphone has:

        Finger-touch UI
        Full browser
        Multimedia
        Object-oriented managed language runtime for apps
        3rd party apps use the same technology as built-in apps
        Search integration
        Maps and navigation

        If you are missing more than one of the less-important items on this list, you are not really selling a smartphone as customers currently define it.

        Share
      2. @Zigurd

        It’s the big analysts who define what a smartphone is. You could argue that there is sub-categorisation is required and I would agree to an extent.

        However, stating that a smartphone must be touchscreen isn’t really logical considering RIM’s portfolio is largely non-touchscreen based. If you put that kind of criteria in there then you could equally argue that anything without a QWERTY keyboard isn’t a smartphone either.

        Share
  4. Good points. In my opinion, another reason could be that a large number of Nokia phones are sold in developing nations which may not have the same appetite for apps as the developed world.

    Share
  5. I totally agree with the lack of quality in Nokia’s software, but not in all models. Nevertheless it still ranks first in popularity, but…not for a long time I think. If Google presents its own Smartphone, I guess this new device will conquer the world

    Share
  6. All these points are valid but there is one other factor that needs to be added.

    The revenue split offered to developers is less than half of Google and Apple stores. Developers are receiving less than one third of the total revenue and most wait seven months for payment.

    The primary benefactors to a developers work (and it’s hard work developing for Nokia) are the Finnish Government who receive 22% of the revenue and the network operators who get 50% of revenue. When Nokia takes their 30%, there’s very little left for the developer. Network operators hold developers revenue for 180 days and Nokia then holds the revenue for a further month.

    Ovi is not competitive. Nokia management seem to be oblivious to their competitive problems or worse still they appear too arrogant to rectify the problem.

    Even if they had a phone comparable to the iPhone, and the app sales figures where comparable, the terms offered need to be addressed before developers will return.

    Share
  7. 1 correct out of 3 Wednesday, June 16, 2010

    Cak: Nokia’s share in the smartphone segment is actually larger than its share overall in the mobile business. So that’s not the biggest point.

    Also the momentum explanation is bad. The ones losing to Apple and Android in the smart phone segment are windows mobile and RIM according to latest research.

    Ovi is not perfect but it’s not the explanation either. If the phones are good and apps are good then people will forgive a worse shop.

    Having quite a lot of experience in this area for the past ten years I’d say that the biggest issue are the poor development tools for symbian and the poor application portability from device to device which means that no single Nokia phone probably has a critical mass from the developers’ point of view whereas iPhone has 50 million devices that can use the app you develop. Small screens and the lack of touch screen phones is potentially an issue too as the usability of an app is crucial for its success. Nokia has mostly produced phones with keyboards keeping the screen small.

    It’ll take a year or more for Nokia to address these through launching new phones and offering Qt development tools and of course to sell enough of those new phones to create a critical mass. The means are there already, now it’s a question of execution. Let’s see how long it takes for them to make it happen.

    Share
    1. Spot on!

      Share
  8. Here are a couple of reasons why looking into the future I don’t think Nokia is in such bad shape on the developer front.

    1) They bought Troltech and are switching all app development for smartphone, tablet, pad and anything else they come up with to QT. I know that the old Symbian SDK was difficult to use but QT is far cleaner and should allow with minimal changes building an App that works in both Symbian and Meego.

    2) QT is hugely popular in the Linux community and hundreds of applications should be easy to port. KDE, Skype and Google Earth were all built in QT and crucially it already has developer mind share.

    3) Meego and Symbian are both open sourced and there are signs particularly after Computex that other companies are going to build device using these operating systems. Each time a companay builds a device featureing either of these OSs then it’s a boast to the whole QT ecosystem.

    I’m not supprices that Quickoffice is looking for new ways to make money since Nokia has been including Quickoffice on its phones for years but has recently signed a deal with Microsoft to bring Office to Symbian

    Share
    1. APS, good points and I hope you’re correct. Competition in this space brings innovation and better products to the consumer.

      Share
  9. Nokia needs some fresh ideas, as well as many other OS vendors. Look at Apple — they innovate with high tempo. Every OS vendor, due to time to release pressure, puts some simple stuff (like standard connectors to Facebook and such) on top of a stale OS, but there is not much core innovation happening. Check out for instance the Mobile Community Framework (www.uvamobiltec.com) — this kind of products can propel Nokia or another vendor past the competition. They need some serious stuff in the core, new ways to discover and connect with people and apps.

    Share
  10. As a commercial contract developer I have Blackberry, iPhone/iPad and Android apps under development for customers but I choose to use an N900. Given spare time, I prefer to hack together apps and code for the N900 using QT and Python because, basically, its a lot more fun. It’s fun because its easy, very quick and very rewarding. There is also no RIM or Apple to get in the way. This is all scheduled to move onto Meego and N8. However, if the commercials persuaded our clients to request us to develop on these platforms then we certainly would. We wait (with fingers crossed that it will be soon) for software publishers to buy into Nokia’s story and send us the contracts.

    IMHO, more developers should give it a go – even if it is just for their entertainment. No, I’m not related to Nokia in anyway.

    Share

Comments have been disabled for this post