Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Nokia and Microsoft Team Up in Smartphone Battle
- Thread starter MacRumors
- Start date
- Sort by reaction score
I got the impression that they acquired Qt as their version of Cocoa.
But the goal of Cocoa and Qt are almost completely opposite.
C.
I wasn't going to reply to any more... but if your talking Nokia smartphones, while the average selling price has fallen, is still higher than your claim of $8 ( Remembering, this forum is in context of smartphones and not of both smart and feature phones ).
"Nokia’s average smartphone price fell to 156 euros in the fourth quarter from 186 euros a year before. It discounted its new N8 smartphones soon after their release. "
http://www.bloomberg.com/news/2011-...h-microsoft-to-challenge-iphones-android.html
How so? Symbian Qt is aimed at both the UI and accessing the phones service layer ( in the form of Qt Mobility ). Nokia target was to make Qt for Symbian ultimately a replacement for Symbian C++ in order to make Symbian development easier.
Last edited:
The build cost for an N8 is (estimated) to be about the same as an iPhone4.
But if we assume that Nokia is making $50 on an N8 - then there must be some ridiculously low profits on some other devices to take that average down to 8 euro.
In other words they are selling a lot of those low-end devices at cost.
C.
RIM doesn't have an ecosystem, whereas MS does. It is a much better platform to build upon. Still, what a monumental failure on Nokia's behalf to end up in this position.
Qt arose as a way of writing a single bit of code that could be deployed on multiple platforms. The same Qt code can run on smartphones, desktops and tablets. It's a write-once deploy-many solution. Qt copes with the variable screen-size, variable input method what have you..
That's pretty much the opposite of Apples design model. Each app should be crafted for the device it's running on. Cocoa programmers exploit knowing the precise screen dimensions and input methods to create the most refined user experience.
Same layer, but opposing design goals.
C.
I knew about the multi-platform approach of Qt, which was the nice part of Qt. Qt API is generally nice overall, IMO, very easy to learn.
I'm wondering what Nokia are going to do Qt now - are they going to hang on to it for Meego's sake or off load? Nokia have already said Qt isn't going to be ported for WP ( unfortunately ).
i am quite disappointed by this - i have been faithful to nokia for the reason that they have done their own thing and not conformed to the iOS like side of things. i refuse to buy an iphone because there is no qwerty keypad - and android is oh so ugly.
no where do i go!?
Yet you have an iPad? I'm guessing you take the physical keyboard everywhere u go? More junk to carry around i guess.
Elop Ignored His Own Analogy
Elop's internal memo likened Nokia to a burning oil platform and the people on it had to make a choice - jump into the sea or burn alive.
Well - when you are contemplating those alternatives and you down at the sea and there are 2 resume vessels in the area you make a choice - which one to go for. Windows Mobile7 is a sinking ship - he should have chosen HP webOS.
Too bad he didn't take his own analogy far enough and just jumped into the arms [or is it on to the deck of] his former employer. One would have thought he knew better - unless that was the plan all along.
Elop's internal memo likened Nokia to a burning oil platform and the people on it had to make a choice - jump into the sea or burn alive.
Well - when you are contemplating those alternatives and you down at the sea and there are 2 resume vessels in the area you make a choice - which one to go for. Windows Mobile7 is a sinking ship - he should have chosen HP webOS.
Too bad he didn't take his own analogy far enough and just jumped into the arms [or is it on to the deck of] his former employer. One would have thought he knew better - unless that was the plan all along.
From about 1999 to 2008, WinMo was a boon to small custom device makers. Many handheld enterprise and field application devices benefitted from it.
HTC is an excellent example of a MS partnership turning out well in a big way. Using their own custom WinMo shell, they went from being the quiet maker of phones for others, to being a well respected and growing manufacturer of first WinMo and now Android phones.
And you ignore the 7 or 8 failures in the story I posted.
Android made HTC, not WinMo.
Wirelessly posted (Mozilla/5.0 (Linux; U; Android 2.2; en-gb; GT-P1000 Build/FROYO) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1)
I've also read that Nokia have the rights to modify WP7 more than any other OEM.
AAPLaday said:
I've also read that Nokia have the rights to modify WP7 more than any other OEM.
Nokia Smartphones. R.I.P.
Nokia Smartphones. R.I.P.
I did enjoy my Nokia N95 8GB, but progress since has been too slow. And now they have opted to race the 3rd best horse in the race. That means loser!!
I feel really sorry for developers who had developed apps for Symbian, as they will have to re-compile, test and amend to get working on new Nokia smartphones.
The writing has been on the wall for a long time. Since Motorola, Samsung, LG, and Sony-Ericsson have moved onto other platforms and Nokia market share has fallen, there wasn't enough partners to make it viable.
The choice of Windows mobile 7 is strange. Symbian is Open Source, and you would have expected another Open Source platform, such as Android, or a varient of it, as the basis for Nokia's replacement.
It will be interesting to see what they do with the UI, i.e., keep it as MS have it, or to make it look more like Nokia's normal UI.
As many have said, it's too little, too late. Nokia should have addressed their strategy in 2008, 2009 at the latest.
Phil
Nokia Smartphones. R.I.P.
I did enjoy my Nokia N95 8GB, but progress since has been too slow. And now they have opted to race the 3rd best horse in the race. That means loser!!
I feel really sorry for developers who had developed apps for Symbian, as they will have to re-compile, test and amend to get working on new Nokia smartphones.
The writing has been on the wall for a long time. Since Motorola, Samsung, LG, and Sony-Ericsson have moved onto other platforms and Nokia market share has fallen, there wasn't enough partners to make it viable.
The choice of Windows mobile 7 is strange. Symbian is Open Source, and you would have expected another Open Source platform, such as Android, or a varient of it, as the basis for Nokia's replacement.
It will be interesting to see what they do with the UI, i.e., keep it as MS have it, or to make it look more like Nokia's normal UI.
As many have said, it's too little, too late. Nokia should have addressed their strategy in 2008, 2009 at the latest.
Phil
That is precisely the problem: We're already in 2011 and they're still in version 1! Once they fix all the glitches, Apple will be in version 7.
I was responding to a question asking how many had turned out well.
Pay attention, please
HTC made its first WM phone in 1999, and millions more after that.
It got publicly well known first with its WM 5 and 6 phones, such as the Touch.
Android came after, when plenty of us had grown to like HTC's UI innovations and model diversity.
In any case, these two increasingly irrelevant entities of the smartphone landscape are partnering together because none of the sexy players will invite them for dinner
They're tailored for each other!
They're tailored for each other!
I have a Samsung Focus. It's a very nice phone - BLAZING fast OS.
The only thing that will allow Windows Phone 7 to thrive is for carriers to GET OUT OF THE WAY with software updates and innovation.
The first update was delayed due to carriers wanting to get their hands in the cookie jar with the update.
If carriers keep this up, Win7 is doomed.
The only thing that will allow Windows Phone 7 to thrive is for carriers to GET OUT OF THE WAY with software updates and innovation.
The first update was delayed due to carriers wanting to get their hands in the cookie jar with the update.
If carriers keep this up, Win7 is doomed.