Slashdot Mirror


Nokia and Microsoft Make Smartphone Alliance

pbahra writes "The smart money was right. Nokia has jumped into bed with Microsoft and will produce phones running Windows Phone 7. The cynics would say that, here, we have two lumbering dinosaurs of the technology world clinging to each other hoping that the other gives them a future. Optimists would point to two companies that need each other, both bringing vital components to the alliance. The big winner is Microsoft. Windows Phone 7, while reasonably well received by commentators, has not set the world on fire. An alliance with Nokia gives it access to the world's largest phone maker and its huge mindshare — in many developing nations a mobile phone is known as a Nokia. The biggest loser is MeeGo, the ugly, unloved step-child of operating systems." Nokia wrote to developers, "Qt will continue to be the development framework for Symbian and Nokia will use Symbian for further devices; continuing to develop strategic applications in Qt for Symbian platform and encouraging application developers to do the same."

11 of 479 comments (clear)

  1. Shocking by ThoughtMonster · · Score: 4, Informative

    This is a good read on the whole matter. Writing's a bit crude in some parts but raises some good points.

    These charts also illustrate the point. Nokia is alienating both its development community and its customers. Qt is put on the sidelines. Who's going to develop for a dying platform? A lot of people I know buy Symbian because of the generally familiar UI, which is similar to the Series 40 phones. Windows Phone is radically different.

    Ugh.

    1. Re:Shocking by ThoughtMonster · · Score: 3, Informative

      This whole thing is even more crazy if you take in account that Nokia shelled out more than $400 million for two assets (Symbian and Qt/Trolltech) which are now pushed into irrelevance. Nokia even open-sourced the entire Symbian operating system under the EPL, a huge move unlike what has been done by any company, only to dissolve the Symbian foundation after Mr. Elop joined the company.

      What's more, Symbian and Windows phone are not perfect replacements. As some other posters have noted, the hardware requirements for Windows Phone are egregiously high, whilst Symbian is known to be frugal with hardware requirements because it was built from the ground-up to be an operating system for low-power devices. The user-interfaces are radically different.

      The main issue with Symbian is that it was hard to develop for. This was supposed to be resolved with Qt, but now what? Nobody will develop for a platform that's going to eventually die.

  2. The Register's view on this by ctid · · Score: 4, Informative
    --
    Reality is defined by the maddest person in the room
  3. Re:Rest in piece, hacker friendly mobile future by bemymonkey · · Score: 4, Informative

    The Android bootloader lockdown? What? Just stop buying Motorola devices and all will be fine... you've still got HTC and Samsung building decent phones with completely open bootloaders.

  4. Re:Rest in piece, Nokia by L4t3r4lu5 · · Score: 3, Informative

    Where did my link go? What the hell?

    Attn Nokia: Was nice knowing you

    --
    Finally had enough. Come see us over at https://soylentnews.org/
  5. Re:Minimum Requirements for Windows Phone 7? by secondhand_Buddah · · Score: 4, Informative

    Don't kid yourself about developing nations. I live in one. We have one of the most sophisticated cell phone networks in the world. Almost everyone here has a cell phone because landlines are unfordable for the majority of our citizens. Most phones here can at least run Java. The social network of choice here is called Mxit has been developed using Java for mobiles. Its cheap to communicate via Mxit (much cheaper than SMS) so a large portion of our nation does. Symbian will probably end up dominating this market segment for Nokia, while their smartphone segment runs Windows 7 for the meantime until they find a better strategy.

    --
    Participatory Governance : The only feasible option for a real democracy, where everyone really does have a say.
  6. Re:Rest in piece, hacker friendly mobile future by PseudonymousBraveguy · · Score: 3, Informative

    According to the German Spiegel, Alberto Torres (responsible board member for MeeGo) just left the board. So yeah, MeeGo is basically left for dead.

  7. Re:Rest in piece, hacker friendly mobile future by TiberiusMonkey · · Score: 4, Informative

    Apart from Google selling root friendly Android phones, as well as some small independent handset makers selling root friendly Android phones, HTC selling phones that can be rooted with a mouse click and the only actual handset maker to back up your claim of locking down the bootloader that I know of is Motorolla. Also Microsoft is embracing the hacker community over Windows 7 phone thus far. So yeah, other than all those phones.

  8. Re:Sell sell sell by GigaplexNZ · · Score: 4, Informative

    Then KDE will be screwed.

    Nope.

  9. Re:Rest in piece, hacker friendly mobile future by h4rr4r · · Score: 3, Informative

    Not even close to the same thing. At least a Nexus has a reasonable open OS that can do real multitasking.

  10. Re:Rest in piece, hacker friendly mobile future by TD-Linux · · Score: 1, Informative

    You seem to assume that the only point of sharing code and APIs is to run desktop applications. This is not the case. If you look at Maemo, Meego, and webOS, you'll find they share many things in common with the Linux desktop - Pulseaudio, d-bus (maemo), libpurple (webOS), SDL (webOS), bluez, WebKit, and many more drivers, services, daemons, and libraries that can be used for both desktop systems and phones. The point of these APIs isn't so that you, as the end user, can run applications written for the API. It's so that developers already familiar with one API can easily write for both platforms. In addition, the many pieces of software used by webOS, etc are sent upstream.