Nokia Meltemi: Homegrown Platform’s Features Detailed

| March 4, 2013 | 178 Replies


We were sent a very interesting slide from an anonymous tipster to our tip line, that we are unfortunately not at liberty to publish - but we are fairly confident the slide is a legitimate Nokia document. The actual slide detailed the planned features to be integrated in all 3 of Nokia’s OSes at the time as well as the Essential/Basic phone features, below is a rundown of what it detailed:



Also included was a list of “Signature Features” :  Voice, SMS, Internet, Color Screen, Camera, inter-connectivity (BT), Battery life, Design Story, MP3.

There has been a lot of speculation regarding the top secret OS, Meltemi that Nokia never went through with, mainly in regards to what it was or could have been. The slide did clarify a decent bit up in terms what sort of devices would have been expected under the Meltemi route, so here’s a breakdown of what I could gather about this ill fated OS.

  • Meltemi was never as many claimed, a sole companion to Meego or Windows phone, the slide clearly shows a road-map  that has room for both Lumia devices as well as Ashas alongside Meltemi.
  • Meltemi was set to have the same core Nokia features found in Windows Phone and S40, including Nokia Maps and Music.
  • Meltemi was supposed to have a lot of “smartphone” features, things that you wouldn’t usually find in a low end/budget phone, such as a CBD, video calling, cloud storage and the renowned Carl Zeiss camera lenses.
  • “” which as far as I can gather is just that,a site for people to share their own skills/talents with others. This could possibly be an evolution of the “Life Apps” available on Asha devices. – was positioned on the slide as a Meltemi equivalent to “Office 360″ in the Lumia’s meaning it’s possible  it’s some form of document editor/reader. (the “?” in both Asha and Essentials also corresponded to & Office 360).
  • “Social Integration” is listed as a feature but given Nokia’s track record it’s difficult to understand how deep this “integration” goes; seeing how Nokia considered the “Social” app on S^3 as social integration, so this could mean anything from a shoddy Facebook and Twitter app to full blown integration like that in Windows Phone.  
  • Slam Bluetooth sharing, Xpress browser, Journal, Gaming apps and internal storage. 

What I find most interesting is the fact that most, if not all these features that should have come in Meltemi have already been implemented within the cheaper, and already available Asha devices. If this slide is accurate then many Asha features that are already available were supposed to be kept in store for Meltemi, such as Slam Bluetooth sharing which has been out for a while now. In fact with the latest Asha design leaks we can see more and more of these features, such as the “craftsmanship” in the dual shot cover, and that 5mp camera might very well be a Carl Zeiss.
Should this be true then it’s easy to see why Meltemi was cancelled, if the Lumia range can go as low as it has with the Lumia 520, without “diluting” the Lumia name and losing integrity: and the Ashas achieving everything they have in terms of features. A 3rd OS that just mimics what both the high end and low end devices are capable of doesn’t seen to have a place, especially not in the new cost efficient Nokia.


Category: Lumia, Meltemi, Nokia, Windows Phone

About the Author ()

Hey, my name's Ali- Currently a fifth (and final) year Dental Student from Chicago; studying in Jordan. I love all sorts of gadgets almost as much as I love my cookies! Be sure to follow my Twitter handle @AliQudsi and Subcribe to my Youtube for the latest videos - no pressure. Thanks.

Comments (178)

Trackback URL | Comments RSS Feed

  1. nabkawe says:

    Finally putting people’s mind at ease , now off to saying Meego was everything … :)

  2. Janne says:

    To this date, the part about Meltemi that never made any sense to me was that it would have been a third ecosystem for Nokia to build and maintain – especially weird after they abandoned the two other Qt-based systems.

    Looking at these pictures it doesn’t make anymore sense to me. Meltemi looks like it made more sense as a Qt-based Series 40 replacement, when the strategy was still Symbian and MeeGo. Maybe eventually Meltemi for low-end, Symbian in the middle, MeeGon in the high-end – all Qt.

    That was a beautiful strategy on paper. Too bad Nokia was crap at executing it.

    • Jiipee says:

      Meltemi would have replaced Symbian for sure. One of the main questions in my mind is, if Nokia tried to invlude qt on S40 and if its even possible technically / performance wise.

      If Nokia has to pay the 15-20$ for each WP device, the margins on 520/620 devices are low. Meltemi was to run on significantly lower specs than 520.

      • Janne says:

        …unless Nokia pays less. Remember, part of Meltemi canning quarterly report or around that time was the announcement that Nokia and MS had found a way to make WP considerably cheaper…

        • noki says:

          Janne that is wishful thinking just like wen your wishful thinking thought wp7 was going to do that….

          • Janne says:

            It IS doing it. :) 510 and 505 are a part of the second Lumia generation low-end push of course.

            • Janne says:

              Somebody, anybody, give me one credible source for the $15-20 dollars assumed Nokia is paying for WP8 in Lumia 520? Heck, one source for that number for any Lumia!

              • Viipottaja says:

                Well, as we know:

                “Over the life of the agreement the total amount of the platform support payments is expected to slightly exceed the total amount of the minimum software royalty commitment payments.” – Source: Nokia

                I.e. on net basis the licensing fees over the Nokia-MS contract period is expected to be negative.

        • nn says:

          The funny thing is that actual price doesn’t matter due to the contractual obligation to purchase minimal amount of licenses ($5 billions over file years). So maybe Elop is paying $10 per license, but that only means he has to buy 500M million licenses, which of course he has no chance to use even if he was able to prop up Nokia beyond the death of Universe.

          • Janne says:

            …which Microsoft is paying back in platform support.

            However, still, we don’t know how the licensing deal (including minimum licenses) and pricing has been negotiated or possibly re-negotiated to allow the crazily low price of Lumia 520. Who wasn’t surprised by that price, I know I was, as were analysts as well…

            • nn says:

              MS is paying back for licenses they are sending to Nokia? Maybe you should reexamine the deal again.

              Basically it’s about Nokia throwing real money and all their resources on WP, and MS then lets them use $5 billion worth of licenses. If Nokia fails to use all these licenses then they lost on this deal even if one assumes what Nokia is doing for MS is worthy only $5 billion.

              Whatever they renegotiated, the platform deal framework didn’t changed one iota. Read Q4 results.

              • Janne says:

                I have read them, of course.

              • Viipottaja says:

                MS is paying Nokia real money. It just happens that Nokia’s licensing payments and MS payments Nokia are expected to cancel each other out (in fact, Nokia expects to receive a small net payment).

                “Over the life of the agreement the total amount of the platform support payments is expected to slightly exceed the total amount of the minimum software royalty commitment payments.”

                • nn says:

                  Yep, they cancel each other. So in other words it’s just accounting. What is actually changing hands is all the support from Nokia and licenses from MS.

                  And the problem is that, as is clear now, Nokia’s support is huge benefit to MS, but WP licenses are worthless and Nokia can never use them all, as is also clear.

                  • Janne says:

                    Well, even looking pessmistically like you they are not worthless, Nokia can make cheap Lumia 520s for us to enjoy! ;)

                    • Jyrki Sukula ottaa voiton Ramskista says:

                      But there are those stories claiming how Nokia must be paying 20€ for a WP license. That price must be true even while it’s just pure speculation!

                      That’s why Nokia just has to be making losses with every Lumia they are going to sell.

                      This is one of those stories people want to believe in because they are too good to be not true. It’s like some people are still claiming how the game console hardware makes just losses to the manufacturers. That story is just too good.

                • Janne says:


              • Jiipee says:

                + MS saves plenty of money on mapping data and services. If Nokia has exclusivity on AR tech on MS platforms, that could potentially be big. If MS may freely use the mapping data within their ecosystem (at the price they already paid for Navteq) they made nice savings.

            • kues says:

              For me it is clear that Nokia finally did recognise they have no other way but cut prices at the Lumia low end- hoping enough people will nevertheless buy higher priced Lumia with reasonable margins. Pushing prices down is their last chance- if it doesn’t work out, the next downsizing step (another factory closing down and additional lay offs- i suppose) will happen before Q2 financial results are out…
              Lumia 510 was announced about 4 months earlier with lower specs (and WP7 and no SD slot) but had a price tag of 199$ (excluding taxes)- about 150€. Now Lumia 520 with higher specs at only 139€ (excluding taxes).
              It is even more obvious on the 610, 620 and 720 prices. The 610 at 189€ (late Feb 2012), 620 at 249€ (early Dec 2012) and finally 720 at also 249€ (late Feb 2013).

              I don’t think licensing cost are of any relevance at the moment- as you wrote, the amount Nokia has to pay is fixed (at least while <10million [i suppose <20 million] Lumia per quarter are sold) as are the platform support payments Nokia receives.

              • Marc Aurel says:

                Very sharp analysis. Nokia has realized that the high end phones will not produce them enough revenue, at least not in time, so they are now doing to Lumia what they did to Symbian in 2010, that is bringing the prices down as fast as they can. Even so they is still a gap between the 311 and 520, which was left by Symbian.

                The 311 currently sells for about 75 euros before taxes, so the initial price of the 520 will be whopping 60+ euros higher. I don’t know what’s the street price of 510 currently, but it can’t be much less than 125 euros. Still a big gap in Nokia’s lineup and one that cheap Androids will surely take advantage of.

              • javier says:

                exactly, if you own a hotel with dozens of rooms and have low occupancy over a weekend, you offer crazy last-minute discounts for inasmuch as you price the room above your variable costs (cleaning the room, washing the linen, etc.) and earn a small margin, you expect that income and any extra services used by the guests will help you pay your fixed costs. I don’t think it’s wrong to assume that Nokia’s hotel is big (high minimum licence commitments) and rich customers aren’t staying in, so the fire sale is starting… in other words – if Nokia’s current lumia sales are well below their minimum commitment, the licence price is irrelevant because they pay in any case, so they can risk launching a low margin model to gain market share and, if they reach the minimum commitment level, then constrain the supply or raise the price/change the product mix. Hope this makes sense… :D

                • GordonH says:

                  “Hope this makes sense…”
                  Yeah right on the point. Business sense/logic at Nokia only applies to pushing MS products.

      • mirco says:

        And you think that the development and maintenance of an own OS comes for free? Of course, Symbian, MeeGo, Meltemi and S40 have per device costs.

      • Paul says:

        If they would use Meltemi, they would need money to pay in-house-developers (for the development of meltemiand bugfixing). This is also not for free.

        With WP they probably pay per license, but they pay only the licences they need. In total it could be cheaper to pay a little bigger fee per license than to pay salaries for a given number of developers without any relations to the number of sold devices.

        • Paul says:

          Mirco already mentioned it. I was to late (again).

        • incognito says:

          They don’t pay only the licenses they need – the deal was to have a minimal number of licenses bought by Nokia, whether they use them or not, in exchange for that ~$1B of platform support payments from Microsoft. This number of minimal licenses increases each quarter.

          This quarter the number of minimal licenses in dollars exceeds the platform support payments from Microsoft, so Nokia from now on will be giving to Microsoft more than they receive back. It’s a great deal for Microsoft as they don’t have to worry how much Nokia sells – they will be getting their dollars back. For Nokia, OTOH, if they don’t cover the minimal licenses bought with sold devices – and this is not getting anywhere fast as it stands – it will become a serious money drain, potentially much higher than having their own teams developing the OS.

          • Janne says:

            “Over the life of the agreement the total amount of the platform support payments is expected to slightly exceed the total amount of the minimum software royalty commitment payments.”

            • javier says:

              there’s a point in which Nokia goes from having a quarterly net income (platform support payment from MS to NOK exceeding minimum royalty commitment payment from NOK to MS) to having a quarterly net expense. That point depends on the Q-on-Q escalation of the minimum royalty commitment payment, and according to Nokia’s own filings, it will happen in Q1’2013 (or already happened in Q4’2012, don’t remember the exact Q). So if MS payments helped Nokia survive until now, from now on Nokia will start sending cash to MS.

      • incognito says:

        AFAIK, Qt has already been deployed to various embedded systems and non-general computing platforms (like SmartTVs, various imaging and visualization solutions, in-car infotainment systems etc.) which all employ far lesser hardware (with the exception of the GPU in some appliances, perhaps) than what comes with Ashas these days – if I remember correctly the Asha 311 comes with an 1GHz ARM11 CPU and an unspecified Broadcom GPU, which is more than enough of a requirement to run full Qt suite at a satisfactory performance.

        After all, bar the RAM memory which is not all that crucial (unless you do a proper multitask) since the Qt has a very tiny overhead, it’s the same internals they’ve been using on their latest Symbians (7xx and 808PV) and had they got rid of the accumulated bloat in Symbian and decided to rework the ABI and UI layers as it was originally planned (instead of trying to fit Qt within those artificial constraints) I’m quite sure you’d be hard pressed to notice the difference between them and say the N9, visual/UI/UX performance wise. It’s more than enough hardware to run Qt-based UI and apps.

        And these days, with tens of ARM11 manufacturers (the ARM license nowadays costs pennies), a vastly competitive mGPU market and with RAM never being cheaper, you could easily get those internals for less than $15 a set on bulk order. And then there are low-end SoC manufacturers that could give you equally competitive price where you wouldn’t need to do costly design and manufacture as well. Hell, even ARMv7 architectures are getting cheaper by the day – I very much doubt that nowadays the complete internals, barring the radios, of the N9 would cost more than $40 (I often cite the MP price of a fully packaged ODROID-U2 at mere $89, and that embedded is hardware that is far more powerful than pretty much any smartphone internals available today).

        So, I don’t buy the story that Qt couldn’t be made to run on hardware restricted platforms that the s40 line was aiming at – if it couldn’t Meltemi would’ve never been considered in the first place. The decision to drop it has more to do with politics than anything else. As Janne said – if you are dropping Symbian and Maemo/MeeGo, both of which were meant to converge around the Qt suite, what’s the point of leaving the odd child Meltemi when it couldn’t benefit from the push to Microsoft technologies – Qt inside Nokia only made sense if it spreads across all of their offers.

        Meltemi was probably meant to slowly push out Symbian at the mid and low end (and then the s40 when the hardware prices drop with time) while providing a similar interface, while Maemo/MeeGo was to take the high-end scaling down at most to the higher mid-level. If there is no Symbian, there is no point in either of those from Nokia’s perspective. Qt was never a factor in these decisions – it would do the intended job admirably well had it been given a chance.

        • Jiipee says:

          Thanks for the insight once again. A friend of mine working on Qt @Digia said that there should not have been any trouble getting qt on as40. I remember someone on this blog claiming otherwise. Need to check, what mr Green was saying on developer presentations on the matter. If S40 could have sported qt, the strategy change makes even kess sense.

          • kues says:

            They had no clue what they did. Marco Argenti confirmed in June 2011 that Qt would power “the next billion” (after Rich Green hinting at it at MWC 2011).
            You can still read it on the Nokia developer site:
            “Qt Target the Nokia N9 and 100 million Symbian devices today and prepare to build apps for the next billion.”
            It makes no sense at all to fuck with your developer community twice this way… :-(
            My conclusion is Elop/Nokia had no clear featurephone strategy- but of course incompetent development/developers and/or Mary McDowell will be blamed.

            In the end even S40 development was cut in June 2012, so what’s the featurephone future with Nokia?

          • incognito says:

            It actually makes quite a bit of sense – if you’re going to constrain Qt only for the s40, there is no real value in it. You’d be holding and supporting a huge, cross-platform toolkit just to support your lowest margin devices. That would make a little sense from an economical point of view (of course, there is the angle of having at least a bit of your destiny in your hands etc. but…)

            Of course, the strategy change in global, that caused not to pursue Qt for the lowest-end devices is a whole other topic of discussion. It never made any sense, and it has cost Nokia dearly, but I’ll cry over the spilled milk some other time.

            As for Rich Green, it pains me to watch the presentation, but you can see that they were allegedly committed to pushing Qt and evaluating it for the s40 segment (starting around 3:40 mark) irrelevant of the main strategy, so Qt was most probably planned for it in either s40 or Meltemi form. Of course, a little from that presentation came true – they’ve abandoned the push in this direction far faster than I expected. Why, beats me…


            • Jiipee says:

              I guess I remembered correctly. What I meant was that, if S40 was planned to be equipped with qt and it was fully possible, then the strategy shift made absolutely no sense.

              • noki says:

                It does, meltemi IMO was a victim of wp faliour, imagine meltemi selling today in the Asha area probably around 4-6 million terminals per quarter, featuring what was obviously an smartphone OS, do you think WP pessimal sales numbers could survive vs such an internal competition?? If wp had managed to sell well were it was supposed to shine the upper segments of the market, then meltemy would have had a go as it presented no threat to WP.

                One thing is clear, as things stand in Nokia this days there is only space for WP as a smartphone OS. S40 must remain what it is.

      • nabkawe says:

        Qt was what sucked my friend , Nokia discovered that Qt wasn’t finished in many aspects which along with the US choosing 4G LTE instead of Nokia’s idea of 4g (HSPA+ on crack).
        made the execution suck.

        • Jiipee says:

          That is not what Ive heard of Qt, do you have in-house, dev sources why it sucked, how was it unmature? What Ive heard of Meltemi and Qt, it worked. The latest info on how easy porting Harmattan apps to Sailfish seem to confirm that porting is fast. Ok, sailfish is not yet Qt5 compatible.

          4G couldnt have been an issues, why Meltemi was canned. It was targeted to lower end, where LTE is not yet an issue. That must have caused delays with Meego and Symbian.

    • kues says:

      Meltemi made no sense as Elop/Nokia had no complete vision and strategy for the mobile phones business- the only decision was made about smartphones and the change to Windows Phone. There was “connect the next billion” as motto- but it was never explained. And it seems as nobody at Nokia (esp Elop) had a clue about what it actually should mean either.
      In Feb 2011 Elop told the world that the featurephone business was completely separate/independent from the Microsoft deal- this was the second big mistake in his/Nokia’s strategy.
      Smartphones and featurephones are related and this is true even more now than back in 2010/11. The users are switching from featurephones to smartphones (most analyst houses are expecting overall mobile phone sales numbers to stay flat but expect strong shifting from festurephone to smartphone sales). And smartphones have reached pricepoints previously strongholds of featurephones – just remember Elop’s memo from 2 year ago(!) stating “Android came in at the high-end, they are now winning the mid-range, and quickly they are going downstream to phones under €100.
      Elop/Nokia had/has no strategy for that shift- they lost about 20 million smartphone sales and additionally 15 million featurephone sales Q4/10 to Q4/12. The price gap between Asha full touch and Lumia was and despite crazy low 520 price still is large.
      Asha 311: 92€ excluding taxes
      Lumia 610: 189€ ex tax
      Lumia 510: ~150€ ex tax
      Lumia 520: 139€ ex tax
      And remember 311 is the only Full Touch with UMTS. And it’s way more expensive than the Asha 306 (68€ ex tax) and Asha 305 (63€ ex tax) both with resistive multitouch. The Asha 310 (and it’s twins 308 and 309) has capacitive multitouch, dual sim and WLAN, but still no UMTS and a price tag of 102$ ex tax, about 79€ ex tax.

      There would have been plenty of room for Meltemi touch phones -not to mention cheap tablets- above (and alongside) Asha touch and below Lumia pricepoints.
      Killing Meltemi as the replacement for the aging (compared to Symbian Belle Series 40 Touch&Type and Full Touch are a far worse mess) featurephone platform Series 40 could prove deadly for Nokia in the long run- if not from the Smarterphone acquisition a new OS is derived and presented or Nokia makes another bold move to an external OS like Firefox OS…
      I fear Asha Touch only prevents a featurephone sales collapse for a limited time…

      • Janne says:

        compared to Symbian Belle Series 40 Touch&Type and Full Touch are a far worse mess

        Have to seriously disagree on this one.

        • kues says:

          Why? Why Touch&Type and which Full Touch modell do you have on mind?
          I thought of Nokia 500 in comparison to C3-01 and Asha 311.

          • Marc Aurel says:

            Depends on what you mean by “mess”. 311 is much faster than 500, but of course it lacks many of the features Symbian users take for granted. The basic UI is quite good and surprisingly clean, although it still lacks some important features like cut and paste and smart dialing. It also omits some of the features of earlier S40 versions such as the simple Widgets on the home screen. I suppose the idea is that the pull down notification center replaces them.

            As for Touch and Type; it’s a very straightforward conversion of the classic S40 UI, which in turn is not that different from S60v3 UI, just simpler and less convoluted. Some touch screen functions like long presses are supported, but gestures are not, since it’s strictly single touch. It’s not terribly elegant, but it’s an improvement over button only operation in many cases. The only downside is difficulty of precise cursor placement, especially on the capacitative As a 303 screen.

      • manu says:

        i believe there is still room for a cheaper windowsphone 8 device than lumia 520,and windowsphone 7.x devices now need a good price cut as most of it is still priced higher than the likes of 520/620.and doing the math lumia 510 maybe even 610 can retail for almost same price as asha 311

    • Shaun says:

      Mere speculation but I would have thought Nokia knew that S40 needs replacing at some point and they still had, at that point, Qt, loads of UNIX engineers with experience of scaling it up and down plus Apps from the N9 to re-use.

      You can see how you’d come up with Meltemi as the solution even after the Windows Phone switch. They could have grown their own smartphone platform up from the S40 replacement to replace Windows Phone, should they need to.

      But, Nokia’s decline was too rapid for them. They’re left with polishing two turds and hoping the general public just see the shiny and not the turd.

      • noki says:

        The problem for meltemi was that wp was a disaster and any sort of internal competition had to be terminated. Its that simple.

        • Jiipee says:

          That could have had a small impact on the decision. @zetjotkah tweeted that his griend working on Ulm had said that meltemi can be scaled up too. That could have maintained the resistance against new strategy.

  3. I thought Meltimi is dead! This will be cool if true

    • Michael Faro-Tusino says:

      It is dead. This what what Meltemi had/would have. Think of it as the outdated roadmap

      • GordonH says:

        Think of Meltemi as an OS that was eating into the Lumnia marketshare. Sadly nothing in Nokia is allowed to compete against MS products.

        • Michael Faro-Tusino says:

          That is completely false. Meltemi was cancelled because it was not cost effective for Nokia. It took too long to come to market. Like MeeGo, deadlines were constantly being missed and pushed back. The vision Nokia had for Meltemi was taking too long to coke to fruition, as issue after issue arose. Finally it was decided that it was not financially feasible to continue developing the project when it cost more than the potential it had to bring in ( when n you work out that there would need to be marketing to get the ecosystem kick started, as well as production facilities etc).

          It was NOT Lumia that chose the fate of Meltemi, but rather the mismanagement and financial insecurity of Nokia and the project at the time.

          • zlutor says:

            “It took too long to come to market. ” – according to rumors it has been cancelled only weeks before releasing the first device(s)…

            So, there must be some politics behind – or we can call it simply strategy shift… :-)

            • nn says:

              focusing on core competencies

              • incognito says:

                If what was shown in the past two years is called ‘core competencies’, with the exception of a couple of shiny moments – I shudder at the thought of what their core incompetencies are…

            • Jyrki Sukula ottaa voiton Ramskista says:

              There are also rumors saying that Meltemi was not that ready and it was possible that it would have taken well over a year for the first devices to ship.

              That’s not actually so far fetched assumption knowing how badly mismanaged the OS projects at Nokia were.

              • GordonH says:

                ” Meltemi was not that ready”
                Dude you are too blind to see the politics and power of MS in Finland.

                • Jyrki Sukula ottaa voiton Ramskista says:

                  It’s possible that Meltemi was ready or maybe it was horribly delayed.

                  You really can’t be sure about that.

            • noki says:

              Thats what the people I knew in ULM told me as well..

          • joyride says:

            What about WP? Using your logic it should have been dumped multiple times by now.

            • incognito says:

              It was… By Sony and LG for instance, and it was dumped temporary even by the life-long friend of Microsoft – HTC…

              • dss says:

                HTC have no choice… they signed that patent deal with MS (to protect their andro line), so they are in their pocket.

                I really don’t know why Samsung are still hanging around..

          • Jiipee says:

            Is that based on actual sources or your own reasoning- it is hard to tell from the text.

            Mismanagement seems to be major reason: McDowell failed again. Move to Ulm, which did not have right resources,changing objectives, unproven hw.

          • dansus says:

            Then why didnt they dump it the moment they moved to WP? Makes no sense to carry on development if your changing platforms, must of been more to it than technical, like it was a threat to WP in the middle ground.

            • Jyrki Sukula ottaa voiton Ramskista says:

              It was most probably an insurance.

              If WP was not able to make it to the low end, thay could have pursued the Meltemi path.

              Now it’s apparent that WP can be shipped in the low end. It’s also probable that Nokia will have a 100€ WP phone by Christmas.

              That’s why Meltemi was no longer relevant.

              • GordonH says:

                “insurance” for protecting MS products?

              • Jiipee says:

                I wouldntstart with the conspiracy theories. The strategychange might have some large shareholder pressure, but everything after it is quite logical. Symbian was dying and crashed after Elop frightened the sales channel and competitors attacked, Lumia did not sell as planned and they were running out of cash.

                Its hard to say, how mature Meltemi was. What Ive heard second hand is, that it was fluid and fast – nothing on the apps and features. Looking at the frustration of some devs and

            • noki says:

              Again make no mistake it was WP failure that sentenced meltemi to death. If wp was reasonably successful as they expected it to be, then meltemi would have been selling many terminals by now, plus nokia would have been spending way more licenses than the minimum they agreed with microsoft so they could have not launched the cheep Lumias, so the the price range from 200€ to 90€ would be all open for meltemi.

              but since Wp was a disaster there was no space for any thing that could resemble competition, nokia is having a hard time has it is justifying not shipping android devices, let alone if they had a successful internal real smartphone OS…

              • Capedonut says:

                What actually happened was that they realised that the cheapest android phones would have covered most of the price range of the meltemi, and therefore they had to push the wp into lower price points. In fact you can actually get an unbranded 5″ 1080p quad core for about $200 in china

                • noki says:

                  Yes the only way to be competitive there is toe push the least competitive OS with the minimum hardware range available. Right!

                  • Capedonut says:

                    The ux is quite good on the cheapest wp8 phones so it kind of make sense to push them to lower price points. The fact that the os was unsuccessful at the time is irrelevant, as they were fully committed and had decided to make it successful no matter what .

                    • noki says:

                      Frist….its not that easy for Nokia to make real competitive low priced hardware with wp given how hardware constrained it is, with one company having the CPU/GPU monopoly on it they can make what ever price they see fit.

                      Second “The fact that the os was unsuccessful at the time is irrelevant, as they were fully committed and had decided to make it successful no matter what”, this is simply crazy and worse its not far from the truth, many here say that nokia was overconfident about itself and symbian, apparently the same type of behavior passed to wp, “Consumer will buy what we make no mater what” type of mentality, guess what? they did not and will not.

                • kues says:

                  They knew it 2 year ago- just read Elop’s memo from Jan 2011. So they did wasted money on Meltemi for over a year, if your argument was right.

  4. Grendell says:

    Thats the way the cookie crumbles. I hope we see the harmattan interface somewhere down the line though. It was awesome and shouldn’t be left to rot.

  5. noki says:

    meltemi could also have been a back up plan in case wp went horribly wrong, guess what? it did!
    S40 is a dead end platform, that will bet on html5, (not the best way to create efficient smooth low end apps).

    • Sefriol says:

      HTML5 is a great bet. It will be the future of mobile industry for sure. When this is going to happen is another question.

      Qt was / is a beautiful platform. Unfortunately it didn’t work for Nokia.

      • GordonH says:

        HTML5 is too far fetched and no company should be betting their roadmap on the “HTML5 is future” theory .

        • says:

          while its not the future, html5 devices would suite very poor/low cost markets,

          nokia is proud of its 15euro 105 phone on series 30, alongside the lumia 920 on wp8.

          so maybe
          an ultra low cost device on the html5 platform, alongside the nokia win8rt/pro device.

          • noki says:

            No No No, thats the thing rendering html5 is no easy task, its not trivial at all and pointing it as low end hardware is were they are failing the most… just see all the demos around its pathetic. Takes pretty good hardware to render the full speck of html5 features, you guys should have a look at the full range of things html5 can in theory do its impressive, and knowing how complex some of those things are i can bet that it will still take more than a couple of years till we gets to point were it might make sense, but as usual by then the traditional tollkits/solutions will be doing even more amazing things at incredible speeds.

            plus in html5 platform integration is something that I have to see how its done,

            • says:

              i dont think children in economically poor countries will need to use CAD.

              all a html5 platform device needs to do is be able to run web browser apps.

              • noki says:

                Cad is actually not cpu intencive this days at least, I’m sure most phones would be able to run it at comfortable speeds… (except 3D rendering/shading/raytracing)
                What is cpu intensive is fluid interfaces at 60 fps, Gaussian blur, and all of the modern UI elements one expects from a semi modern mobile app.

                But don’t take my word for it go and see most html5 mobile demos out there, its sluggish and not very efficient, specially wen the hardware is not the best.

                • says:

                  i doubt i child in africa is going to be able to compare a html5 device against a macbook pro,

                  • noki says:

                    No, but he is gonna be able to compare it to the other competition cheaper phone that did not went the crazy html5 way and delivers better experience.
                    They may be poor, but they are not stupid.

                    #note I dislike this western mentality that we can send what ever crap to underdeveloped countries that they will love it because they are soo poor and what not.

                    • says:

                      i have no idea what universe you live in, but you have a major chip on your shoulder,

                      its just impossible to have a discussion without you becoming so melodramatic,

                      i believe you only engage in topics solely to cause drama.

                      who said the poor are stupid ?
                      who said the poor will accept crap ?

                      is the new 105 crap? are people stupid for buying it?

                      my point, again, is that a cheap html5 devices may be the first and possibly only device that children/adults from economically poor countries can afford,
                      AND if nokia is proud of the 105 alongside the wp8 920, then why not a html5 device alongside a win8 device ??

                      some good reading about how “westerners” as you put it, are helping poor school students become connected with the world.

                    • noki says:

                      Your assumption the hml5 is cheeper is Wrong that’s the problem its not cheaper it takes better hardware to deliver similar comparable results.

                      “” It was because I know very well the OLPC program that I say this.
                      The OLPC project is one of the most flagrant example of this and I can share countless stories about it that I know first hand.

                    • Jyrki Sukula ottaa voiton Ramskista says:

                      A phone with only html5 capabilities for applications may seem to be a device that requires only moderate or low end hardware. It’s easy to say that because you can make some smooth web pages with that the browser that phone has.

                      But if it’s supposed to run htnl5 applications with more features and using some hardware intensive features, it’s not going to be smooth. It’s going to lag.

                      Html5 has way more overhead than Android VM applications have. It will lag on low end hardware if some processing power is required.

                    • says:

                      i’m talking about very low cost device,
                      just as nokia built the feature reduced 105 phone for 15 euro.

                      html5 is open, no need to pay ms a licence fee to use android, so cheaper,

                      no need to add hardware for more feature rich web apps available on the html5 platform, so cheaper again.

                      and the market countries for this device don’t even have the infrastructure to supply bandwidth for those feature rich htlm5 apps,

                      for a very low price, i don’t think people would mind
                      if some html5 features can’t run 100%,

                      a Nokia html5 device would be the first “pc/tablet” near billions would be able to afford,

                    • Jyrki Sukula ottaa voiton Ramskista says:

                      Why not create a cheaper device with a support for native applications?

                      Or a device with a support for bytecode. That would perform faster than html5 and it would be cheaper to manufacture because the hardware costs less.

                    • says:

                      because html5 is the open web platform


    • viktor von d. says:

      indeed wp went horribly wrong.that’s why they are releasing a full portofolio of devices based on it.

      and s40 really is dead with html5 being the future. imagine all those people in india and afrika who can barely afford a phone.they will be so happy when they will have smartphones like the ones that run firefox os with webapps,entirely dependent on a internet connection that costs more money.hell screw that,imagine all those people that don’t even have the resources to buy a phone and need to save money for a year to buy a 50 euro featurephone.they will go nuts when they will hear that s40 is absolete and they will have now a more expensive phone that runs web apps.oh the joy

      • Shaun says:

        You’re typing crap.

        Just because the apps are HTML5 based, does not mean you need an internet connection. HTML5 supports local offline storage. Apart from that most of the HTML based OSs have specific APIs to access the local runtime and hardware.

        Firefox OS has a Gecko runtime with APIs to access the Linux stack underneath it via their Hardware Abstraction Layer.

  6. SLAYER says:

    meltemi could have replaced S40 altogether. I guess the evleak was a meltemi device.

    • chandan says:

      If u see smartephone acquistition by nokia,something development is going on. As smartephone os is based on linux.They are worked on linux based os.The right way here comes now to Launch meltemi at Low end based on linux while Windows phone ecosystem at middle and higher end.With dominance of android which is linux based,if part of itellectual engineer thought of dominance of another platform.So nokia decided to support WP platform.Now i think that time has come to launch …. nokia true os ecosystem

  7. et3rnal says:

    How old this map is??? could Meltime be still under developing ? could the latest lakes belongs to it? any chance?

    • Luisito says:

      No chances to see anything… If Nokia is developing an OS, it’s and evolution of S40, and still I won’t hold my breath waiting for that to come true…

  8. Paul says:

    Probably TYPO,
    but AFAIK it is Office365 (not 360)?

  9. Silthice says:

    One big problem will be the apps as all three OSes WP, Asha and Meltemi featured different type of Apps support. The original Plan was Meltemi, Symbian and MeeGo with integrated Apps using QT. The main setback of all OSes beside iOS and Android are the Apps unavailability that make most of the people hard to leave iOS and Android camp as they common apps that they used there are not available in other Platforms.

  10. Jiipee says:

    “Social Integration” is listed as a feature but given Nokia’s track record it’s difficult to understand how deep this “integration” goes”

    N9/swipe UX style of social integration with sone refinements would have been great. All they need to add was filtering of events from tje feed under a contact. It already has the latest update on the contact form.

  11. darkside says:

    Nokia is like serbia, saller and smaller…and biger propaganda…but nokia presents to you the ASHAAAA and Dallai Lamiaaaa….

  12. Weirdfisher says:

    asha s40 still cant compete with cheap android

    cheap android is still an android-at least it has got all the latest top grossing apps for android such as candy crush, temple run 2. but asha is nowhere near windows phone. It has a huge gap between the 2 OS es. In the past, Qt was meant to link up the platforms. But after adopting wp it immediately break up everything.

    • viktor von d. says:

      i’m sorry but you talk out of your ass if you think sub 100 dollar androids can run all the apps and games android has to those price points you are lucky if you get a 3.5 inch screen, a 1 ghz processor and 512 mb of ram. not to mention a hvga resolution and gingerbread.maybe ice cream sandwitch if you are really lucky. and no temple run 2 won’t work on those devices and android is crap on 512 mb of ram.

      and how can you say they can’t compete with android at those price points, when ashas are selling really well and are forcing nokia to release variants with wi-fi of the phones

      • kues says:

        >and how can you say they can’t compete with android at those price points, when ashas are selling really well and are forcing nokia to release variants with wi-fi of the phones<

        Perhaps because despite Asha full touch Nokia is still loosing featurephone sales?
        And e.g. the Sony Miro has about the price of a Asha 311- with a Qualcomm MSM7225A (with Adreno 200 enhanced GPU) only a bit less powered than a Lumia 510 or 610. And don't forget the no-name Android.
        Btw: Asha 306 already had WLAN (as the Asha 311) last year- just no Dual-SIM and only resisitive Multitouch. The 308/309/310 got capacitive Multitouch as the 311 had before.

        • viktor von d. says:

          they were loosing sales,the asha full touch stoped the droped and started increasing numbers

          • kues says:

            Only in Q2/2012 featurephone sales were slightly higher YoY. Full year 2011 to 2012 Nokia lost over 39 million smartphone sales- more than 10% lost! Moreover Asha Full Touch only stopped the ASP drop- flat on 31€ since Q2/11. Featurephone revenue full year 2011 was 11,9b €, full year 2012 below 9,5b €- over 20% revenue lost (contribution/operating profit dropped from over 1,4b € to 551m €).
            Asha Full Touch probably slows down the decline, but can’t stop it.

            Featurephone sales
            Q1/11: 84,3m
            Q1/12: 70,8m

            Q2/11: 71,8m
            Q2/12: 73,5m

            Q3/11: 89,8m
            Q3/12: 76,6m

            Q4/11: 93,9m
            Q4/12: 79,6m

            btw: 2010 sales, revenue and profit on featurephones was better than 2011

        • kues says:

          Of course it’s the Sony Tipo not the Sony Miro i was referring to. Mixed up the names.

  13. GordonH says:

    All business logic sense at Nokia has to be about pushing the MS mobile ecosystem. Meltemi was cancelled for no other reason. Quote from the article.

    “Meltemi was supposed to have a lot of “smartphone” features, things that you wouldn’t usually find in a low end/budget phone, such as a CBD, video calling, cloud storage and the renowned Carl Zeiss camera lenses.”

    It been 2 years and I am still never wrong when I say that “All Nokia products competing against MS products will be strangled, stabbed or killed(live on).”

  14. EK says:

    To an outside observer S40 has turned out to be a surprisingly agile, productive and flexible OS. Is there some technical fundamentals for the seeming ease that S40 has evolved during the past 2 years ? Or is this simply result of massive investments in execution of “Internet to the next billion” strategy ? Even a horrible OS can be made to look good ?

    • kues says:

      You are right: a horrible OS can be made to look good. In my opinion it’s even more true for S40 than for Symbian.
      S40 Touch&Type is a real mess. If it was hard on Symbian 3rd and 5th to find certain configuration features, S40 Touch& Type is like additionally being blindfolded. Asha full touch is of course fancier than Touch&Type but the ugly face is lurking below- just try to configure VoIP on the 311 after doing the same on Symbian Belle.
      And S40 lost Maps features: Nokia 2710 was a full blown turn-by-turn navigation device with build in GPS. The new S40 maps application can’t even use an external bluetooth GPS device!

      If i think of Asha 311 and Nokia 500 being sold at same street prices today, only the fancy dress of the 311 could magically hold me back from chosing the Nokia 500.

  15. viktor von d. says:

    this must be since the microsoft deal was signed, because all those lumia features refer to high end devices and the standard clearblack,carl zeiss features refer to meltemi devices. i think when they signed the deal with microsoft they expected to have windows phone/lumia only for the high end devices like the 920/820 and a full pureview. while the mid range and low end smartphones would have runned meltemi. and then the asha we all know.

    i think they figured out that they can push windows phone to reach the low end with devices like the 520 and 720 while also keeping a few running wp7.5. this while improving asha,and i think it’s a good strategy. we already see wireless charging,clear black,supersensitive screen and carl zeiss cameras in the 520 and 720.

    i think it would have been madness to have 3 platforms wp,meltemi,asha plus the basic feature phones. big costs, lots of efforts to court developers for meltemi in parallel with asha and wp.

    only things i wonder is why didn’t they replace the asha line completely with meltemi devices and opted for the smarterphone aquisition to improve asha.

    • noki says:

      meltemi would have probably goten out if WP was not such a disaster, as it stand if meltemi would have sold a few million it would have been terrible competition internally to WP… Its that simple meltemi had to die.

      • Luisito says:

        Alogn with Symbian and basically everything that could take Nokia apart from the wonder OS called WP…

  16. Thomas F says:

    A small jolla (lifeboat) was put in to the wather, so that the core of the real Nokia will stay afloat, if/when the big ship should go down. Sailfish will be there if WP fails.

    • dss says:

      At this point its almost impossible for WP to fail.. Nokia will give every last ounce for it to get some tracktion, and by then even if Nokia fails, WP will be fine since it will be significant enough for Samsung to put some weight behind it, and Microsoft will have their own phone as well.

      The key period is the next 15-20 months, and I am pretty sure that WP is safe under Nokia’s wing.

      • dss says:


      • noki says:

        All depends on how NSN does and asha line, if they stop providing the profits we will soon see nokia selling “here”, and then other fundamental areas.

        Lumia line is just a massive money sink

        • capedonut says:

          “Here” is pretty much the reason why they went wp in the first place

          • noki says:

            becouse????? are you talking about android not allowing Nokia maps in android? because if you are that is just nuts, nokia could have bundle what ever apps it wanted in its phones.

            • Jyrki Sukula ottaa voiton Ramskista says:

              Bundle, yes, but replacing the default applications for maps, no.

              If an application wants to use maps and calls the Android API for that, it will show Google Maps. That’s something Nokia was not allowed to change.

              Using Nokia maps only for that application and not for all of the applications using the map data is not that tempting.

              • noki says:

                speculation game, but fair arguments if true…Personally all i want is that Nokia ports “here” to BB10 would certainly not mind paying for the app.

                • Jyrki Sukula ottaa voiton Ramskista says:

                  As far as we can tell, this seems to be the situation. Google wants to prevent the platform from fragmenting and maps is something they will not allow anyone to change. It’s the feature of the platform. Just like the default store for applications.

                  You can add additional applications, but changing the default one can’t really be done.

                  What would happen if Nokia has maps on the device but the applications would open the Google Maps? At least the user experience would be not that balanced. People would not understand why the device shows something on one map and then it’s gone on the second one.

                  That would be a mess.

                  • Gordon says:

                    The fact is, you CAN change the default applications in Android. When you choose third party application as default for maps and navigation, Google Maps isn’t opening anymore.

                    If an application wants to use maps and calls the Android API for that, it will ask which application you want to use if there are more than one options.

                    Your widely spread argument is totally false.

      • Marc Aurel says:

        Impossible to fail? Sure, WP will not fail in the short term (12-18 months), but it’s long term future is still almost as uncertain as it was a year ago. It only requires Nokia to abandon the platform or be sold to a company not interested in WP, and WP is history. MS can’t sell their own phones even if they had them. Just see how well the Surface tablets are selling and they are not very dependant on existing carrier relations, unlike phones.

        You don’t seem to realize how beleaguered the WP platform still is. Microsoft’s position as the leading PC OS provider did not save WinMo from increasing irrelevance, and it won’t save WP if Nokia fails to grow the platform at least at the same pace as the market, that is maintain market share. In fact only strong market share growth will guarantee WP’s future beyond 2014.

        • v.s.i says:

          Surface Pro is a really good tablet, which should get even better with Haswell. Oh, and some usable cameras, hear that, Nokia? ;)

          • rim says:

            Yes nokia needs to spend more money in the promotion of Microsoft products. Because all we need is cameras on absurdly pricey tablets.

            • v.s.i says:

              Nokia should make a W8 tablet with a good camera some day. But you obviously can’t take a bit of a joke or distinguish one from reality, can you?

              • Jiipee says:

                W8 tablet could fit Nokia’s lineup. There are several things to consider though:
                - how ca they digferentiate?with apps and camera?
                – do they have competitive terms for Windows licences against eg Samsung with full portfolio?
                – do they have to rewrite all their apps and camera software yo W8? Do they have reources and competence?
                - would they get any support from ms?
                - could wp be scaled up to tablets?
                – are the sales channels different for tablets, what is Nokia’s position there?

        • dss says:

          The reason WinMo didn’t work for MS was because of Nokia/Symbian… this time around they have Nokia on their side, so I think they are pretty safe.

          They do have to worry about google/Samsung/moto .. but I think there is enough market share for everybody out there.

          Long term, I don’t think most people realize how important for MS Nokia really is … they are essentially saving their mobile platform from failing, for the 2nd time.. Microsoft CAN NOT afford for that to happen, and it won’t. They will get to 10-15% market share and from that point on they will be fine..

          As far somebody buying Nokia in the meantime, if anyone would, it would be either the Chinese or MS.. or some sort of combinations of the two. Microsoft won’t let that horse go that easily, they simply can’t..

          I am very confident that the WP project will be fine in the long term, can’t say the same about Nokia, unless they downsize further.

          • Marc Aurel says:

            You seem to think that MS can throw endless resources at WP. Even if they theoretically could, they don’t seem to be doing that now, either. Where is FM radio support? Or support for quad cores and 1080p screens? When are they coming? What about fixing the “Others” storage bug?

            For a project that is usually considered to be Really Important for Microsoft, they are actually developing it at a relatively unhurried pace, not that differently from recent desktop Windows development, where they already dominate and can easily afford to take their time. To me this indicates that they are already preparing for the possibility that WP will ultimately fail and do not want to throw any more resources at it than they already are.

            Microsoft does not really need the smartphone market to survive and thrive, either. The tablet market is what they really need and what they should concentrate on, not the smartphones.

            • noki says:

              I agree with dss, only way that I can see MS giving up on mobile is if they start to take a real hit on the desktop area, as it is its to vital for them to become big enough in the Mobile space, so their technological range of solutions keep on being a standard and Microsoft remains Microsoft.

              The question is???? Will they start to take a hit on the desktop????? As I expected Google is now starting to take a look at that segment… Will it be a problem??? time will tell….

              • noki says:

                As for nokia? Nokia is now just a another victim of Microsoft usual relationship paradigm, come to bed and die, or get very very very sick.

                To be honest companies that go to bed with Microsoft are already in desperate mode this days.

      • AreOut says:

        yeah Nokia will give every last ounce for it to get some traction…and then MS will dump Nokia or buy it for some cheapo money.

        Very good business of one must be compensated by very bad business of second, its the basic market law.

        • dss says:

          Oh ya.. that was pretty obvious from the moment that silly contract was signed :) We will have to wait and see.. the EU won’t be happy if MS buys part of Nokia, not happy at all.. so if they are going to do it, they will have to get creative again.

          • noki says:

            bffff there are plenty of Microsoft controlled “investment funds” that can do that.
            Those funds will them brake it a part a sell anything of value back to Microsoft (if they see it as interesting for them) the rest is left to die and dry. Its not like they haven’t done this before.

        • Jyrki Sukula ottaa voiton Ramskista says:

          The alternative?

          Going out of business with Symbian and MeeGo.

          Remember that neither was really competitive and those two cost more than WP.

          Elop probably saved Nokia.

          • GordonH says:

            I already told you so many many times… Facts don’t change by repeating lies.

            • Jyrki Sukula ottaa voiton Ramskista says:

              That’s why I’m not telling lies.

              Unfortunately Nokia was collapsing with Symbian and no one has presented any real reasons why they would have succeeded with MeeGo.

              • Marc Aurel says:

                You mean reasons you would accept? Because it’s quite easy to demonstrate that MeeGo was much better than Symbian and in some ways better than WP or Android as well.

                But in any case, since we are speculating, the burden of proof is not clearly on either side of the debate. There is no “default value” in counterfactual speculation (i.e. alternate history) concerning complex matters. If you say something would have happened, you must provide the reasons for it, if you want to make a rational argument.

                • Jyrki Sukula ottaa voiton Ramskista says:

                  Very true.

                  I have already pointed out that Nokia was in a position of selling most of the mobile phones they manufacture, to those people who were already customers of the company.

                  They were also selling less and less mobile phones in the high end. Most of the sales were just low end phones.

                  I just don’t see anyone explaining how they were supposed to start selling those high end MeeGo phones to the customers who were buying low end phones. That makes no sense.

                  Trying to get Android or iOS users to buy a MeeGo phone would have been pretty much just as hard as it’s to get those people to buy WP phones. People have already invested time and money to the iOS/Android ecosystem and it’s really hard to convince those people to change OS.

                  • Jiipee says:

                    So your point is that, if nokia wanted to sell high end, they should have chosen Android?

                    Or alternatively, to maximize sales – and probably profits – concentrate on low-mid end? Depending how mature and ready to sell Meltemi was, they could have disrupted low- and mid price points and probably get the high end prices down.

                  • Jiipee says:

                    So your point is that, if nokia wanted to sell high end, they should have chosen Android?

                    Or alternatively, to maximize sales – and probably profits – concentrate on low-mid end? Depending how mature and ready to ship Meltemi was, they could have disrupted low- and mid price points and probably get the high end prices down.

                    After the base work was done, they could have sacked 50% of the project devs to cut costs. Also, they should have organized a bidding competition, who will get to.become the default search engine. Mozilla and Apple receive nice amounts from Google. (I will never understand how narrowly BoD and elop saw ecosystem, if they only contacted Google, Ms, Rim et al)

                    • Jyrki Sukula ottaa voiton Ramskista says:

                      Probably yes, but it would have resulted some other problems. It wouldn’t have been possible to change the maps provider for apps, no changes to the search engine beyond what the manufacturers have done now. Just an additional store for applications and probably less evolved one compared to the store Google is offering.

                      Even with selling Android phones, there would have been lots of competition. Not as fierce as it’s today, but also a world of competition where the old Nokia services like maps can’t be used.

                      That would have resulted problems to the low end. Having Google maps there could have proved to be difficult. Also it was already obvious that Meltemi was not ready to take on the low end. It was not ready when the Asha series was launched. What are the realistic chances that it would have been ready in time? Nokia just didn’t have the talent for the management of the OS development.

                      In a probable best scenario Nokia would have shipped the first Meltemi units barely for the Christmas time. They would be starting the colume shipments at this time. But it’s actually quite late for that.

                      Android is already hitting the same price point Meltemi was targeted for. It was supposed to start from 200 and moving down to 50. But it’s pretty obvious that the 50 device was not going to ship anytime soon. That strategy was never the Nokia way.

            • v.s.i says:

              What lies?

              Is it really even believable that the E7 and Galaxy S 2 launched in the interval of a couple of months from one another? Could Nokia have continued to sell 680 MHz ARM 11 CPUs and nHD screens, let alone paired with Symbian, and expect to best Samsung’s flagships with them?

              MeeGo is another story, maybe it would have turned out better than WP. But, for the time being, neither you nor I run Nokia, so the best we can do only sit and watch, and if you support the company, buy products every once in a while.

              • kues says:

                a) Nokia deliberately choose the low specs for the first Symbian^3 devices. Symbian wasn’t the limitation- Nokia could have choosen higher powered Cortex A8 or A9 cpu and/or higher screen resolutions.
                b) Flagship devices was Meego responsibility. And N9 specs are quite similar to Lumia 800 specs- but N9 arrived earlier. And no one could have stopped Nokia from shipping a dual/quad-core Meego device with 720HD screens in H1/2012.

                • Jyrki Sukula ottaa voiton Ramskista says:

                  It wasn’t Elop who decided to ship N8 and E7 with underpowered hardware.

                  Nokia was already failing in 2010.

                  All they had left was to compete with price.

                  • kues says:

                    Yes, it wasn’t Elop he decided about N8/E7 hardware. But it was Elop who decided the next Symbian^3 hardware platform (600/700/701) was not allowed to run at full cpu speed when sales started.

                    Nokia didn’t fail in 2010, they failed miserably in 2008 and 2009.
                    2007 to 2008 full year smartphone sales stayed flat (60,5m). But Q3 and Q4/2008 YoY smartphone sales were lost! Marketshare declined Q4/2007 to Q4/2008 from about 46% to 31%, sales numbers from 18,8m to 15,1m.
                    In 2009 smartphone sales almost stayed flat- expect Q4/2009 which had a big boost (5,3m YoY, 4,4m QoQ) and lifted marketshare up to 39% again. And 2008 to 2009 34 million featurephone sales were lost!

                    But 2010 finally saw light: Meego/Maemo was finally elected for high-end over Symbian, mid-year 2010 Symbian and Meego development was sorted out. And cuts on Symbian development budget were on the way for H2/2010.
                    And on the sales side Nokia drew their wild card for delayed Symbian^3: Jan 2010 turn-by-turn navigation was made available for free on Symbian. Combined with price cuts and finally Symbian^3 arriving Nokia managed to increase smartphone sales by over 33 million, that way despite price cuts revenue increased and SP division stayed profitable. Even the arrival of the iPhone 4 with it’s retina display in Q3 and Q4 (lifting iPhone sales up to 14 and 16 million) did not stop that- but smartphone marketshare dropped back to Q4/2008 level 31%.
                    Was Nokia glorious smartphone market leader and well of (like Mr. Ahonen likes to cry out aloud)- no, but Nokia managed to compensate 13 million featurephone sales lost with 33m smartphone sales gained. Nokia was strong in the mid and low end smartphone market. Not beautiful and far from Apple’s immense profits, but ready to convert it’s featurephone users to higher profit smartphone users and defend the customer base.
                    Let’s not forget Nokia achieved US carrier deals (first in years) for 2011 Symbian^3 devices in 2010- and carrier deals for Meego devices also.

                    But instead of standing ground Nokia cancelled their ecosystem (and carrier deals) and missed smartphone market increase in 2011. Resulting in loosing 34m smartphone and 12m featurephone sales 2010 to 2011. And 2011 to 2012 an additional 32m smartphone and 39m featurephone sales.
                    So guess what’s left to them in 2013: try to compete with price. Unfortunatly with even lower (if any) margins and already loosing money…

    • StefanP says:

      No, not a lifeboat was put to water to save the “real” Nokia, but a group of the best and enthusiastic engineers escaped the chaos and mismanagement of this real Nokia to have a chance to continue to work on an innovative OS.
      It has always been said that Harmattan and Meltemi were too late. See what Jolla can do without the that big organization in their back! Development seems to have accelerated!
      Nokia can still do good HW, but it’s no good place for an innovative OS. It’s good that the Jolla team is on their own now. Give them some time and we will see great results!
      Nokia might beg Jolla to get a Sailfish licence once a BB10/N9 like UI becomes popular and is possible to run on low spec HW plus yields a long battery life. ;)

      • capedonut says:

        I kind of agree. Nokia didnt have the luxury to be able to wait and see if meego or meltemi would take off. Although microsoft has sucked pretty badly at mobile, they usually get things right…eventually. Xbox as an example

  17. Dr.Smart says:

    Nokia’s aspiration is to become an OEM ever since Elop. That’s all there is to it.

    • dss says:

      More like Elop’s aspiration.. and he made it happen.

    • Jyrki Sukula ottaa voiton Ramskista says:


      Maybe Nokia wanted to stay as an OEM. After all, Nokia was practically an OEM already when they were manufacturing Symbian phones. They were so constrained by the limitations the in-house OS development had, that they really were just an OEM.

      They really had very little control over the competitive features they had in Symbian.

      Luckily they have the Asha phones.

      • kues says:

        Yes luckily they have Series40- delivering years too late on dual-sim and touchscreens. Thinking in double-standards?

        • Jyrki Sukula ottaa voiton Ramskista says:

          Apparently they can develop and sell Asha phones. Apparently Elop allowed the development on S40 while OPK did not do that.

          They didn’t have the talent for developing Symbian effectively. There is a big difference in that.

          • Jiipee says:

            OPK was fired and the alternative to Elop could have supported s40 as well.

            I highly doubt that elop paid much attention to feature phones personally. To make such claims as you do, you would need to know a lot more on what was going internally.

            I would love to hear, what mr Green managed to do before Elop joined and the first months, when Elop was still learning names.

            There muat have been potential younger talent within Nokia, who could have taken the lead (not Ojanperä) and have a quicker start. If you know anyone, who worked for Nokia late 2010, everyone felt the need for change. Even OPK, who had at minimum approved Meltemi development and launched the design driven N9 development. He had hired Skillman and Ahtisaari, who seem to be valued by Elop. (Im not saying OPK was good, but he was not complete failure either. He just continued Ollila’s footsteps with no software understanding)

            Disclaimer: I believe that WP will sell enough to keep Nokia in the game. Im not saying Symbian had long life left. I dont know enough what was going on with Meltemi and Intel cooperation. Im sad that Nokia destroyed their sw competence, when they finally may have had competent VP. Im pretty sure that Qt ecosystem would be at minimum on the level of WP ecosystem and the net present value for Nokia would be higher than the future cash-flows coming from MS ecosystem

            • Jyrki Sukula ottaa voiton Ramskista says:

              I’m saying that Elop allowed the development of the S40. Not that he really pushed that.

              They still seem to have some horrible managers, but we will just have to wait and see how this turns out.

            • capedonut says:

              “Im not saying OPK was good, but he was not complete failure either. He just continued Ollila’s footsteps with no software understanding” I think that is more or less the root of the problem. You have a CEO who doesnt get or care about sw, how can you then expect him to hire the right people.

              • Jyrki Sukula ottaa voiton Ramskista says:

                For the long term OPK was a complete disaster.

                He even hired apparently highly incompetent people and some of those people are still working for the company.

            • marees says:

              I dont agree that an alternate CEO to Elop would have focussed on s40. It was very clear from Nokia’s history that both Maemo and s40 development suffered due to politics by Symbian platform team. Only mistake is instead of going Android they went WP. That too 2years were lost in WP7. It would have been better for Nokia to release on WP8 first and till that produce Android phones as a back-up. But thats my opinion. I dont know what forced Elop to make the decision he did to go all in on WP7.

              Even more ridiculous is that if MAPS was Nokia biggest Asset then they should have gone for 5″ or 7″ devices and WP will support such devices only next year. Aaaarggh :-(

  18. Tom says:

    I am wondering why we can’t see the original slide?

  19. Enchong Dee says:

    Uterus lol

  20. Nathan says:


  21. You can certainly see your expertise within the work you write. The world hopes for even more passionate writers like you who are not afraid to say how they believe. Always go after your heart.

Leave a Reply