Nokia to launch new Windows Phones every 2-3 months

Although there is still no official word on when exactly Nokia’s first Windows Phone devices will be out – it may happen before or after the end of 2011 – today the company has provided some extra details on its WP strategy.

According to Jo Harlow, Nokia’s executive vice president of smart devices (who was quoted by PC Mag), new Windows Phone devices should be launched “in a rhythm that might be every couple of months, every three months, something like that.”

With new devices being introduced at such a fast pace, we’ll likely see handsets of various forms factors and price points pretty soon (for example, we’ve heard that a Windows Phone E 71 / E6-like handset is in the making).

Nokia is also seriously considering manufacturing CDMA Windows Phone handsets for North America – which wouldn’t be a bad idea at all, since Verizon and Sprint serve about 150 million customers together, and may help Nokia sell a few smartphones.

Jo Harlow hopes that Microsoft’s strong relationships with US carriers will allow Nokia to make a splash on the US market.

As mentioned earlier this week, the first Nokia Windows handsets will run Windows Phone Mango (which comes with about 500 new features, so it should be a quite capable OS).

Author: Florin

Share This Post On
  • http://profiles.google.com/wmarkjones7 Mark Jones

    Despite all this hopeful talk about the possible bright spots in WP7’s future, there is an elephant lurking in the closet.  That is, Microsoft’s support for Windows Phone 7 app development is very weak.  Although new ISVs developing apps will (and probably already have) discover that Microsoft’s development software and the .NET subset for WP7 is very strong, the maturity of MSFT’s overall app-developer support structure is just not there.  In the long term, that can only result in continuing lackluster performance and ultimate failure of the Windows Phone 7 product line in the global marketplace.  Not good for anyone, especially for Microsoft.  So what are the problems with Microsoft phone app-developer support?
    First, an app developer cannot expect real, solution-oriented responses to technical questions about WP7 app development through MSFT’s App Hub and Visual Studio “Feedback”, the primarily facilities for phone-app support available to most developers.  But in fact, only those ISVs fortunate enough to have (a lot of) money for annual MSDN subscriptions can expect to receive actual support.  The very large majority of app developers are thus left out in the cold, able to depend only on each other via the App Hub and MSDN community forums and for advice and help.  Microsoft is basically and officially unhelpful in my experience.  App Hub and/or Visual Studio queries are met with non-helpful, non-solution, and superficial responses, which are only a further waste of the developer’s time.  (Ironically, if a new ISV becomes successful enough via sales, presumably they will have the funds to pay for real support.  But the lact of real support up front hampers their chances of success.)
    Also, app-devs hoping to see their cool new app appear on user searches in the Marketplace will quickly stop hoping.  Microsoft has placed an arbitrary 20-item limit on search results that appear when either a phone or a Zune user enters search keywords to find a particular category of app.  Only 20 items appear!  For new apps, this is a show-stopper.  The gist of the problem is that the only way an app will appear on this tiny, 20-item “leader board” of apps, and therefore even be visible to most users searching for it, is that the app is a top seller.  But the only way to become a top seller (ostensibly) is for the app to appear on the search-results leader board.  Gotcha, new WP7 app-dev.  Another catch-22.  Try to work your way out of that one.
    Finally, leave it to Microsoft to add insult to injury.  Struggling new app developers can expect monthly income from app sales only if the sales credit exceeds $200 monthly (the sales credit is the amount left over from sales after Microsoft takes their 30% off the top).  Now $200 sounds like a small amount, even for leftovers, but it’s nonetheless a significant, tangible indicator of startup-success to a new app dev, regardless of the fact it’s a drop in the bucket.  But if the leftovers monthly don’t exceed $200, the app dev doesn’t see a dime of that.  So it’s simply the principle of the thing.  These payments are disbursed via a computer server that cycles monthly and issues ACH (electronic draft) deposits into the developers’ accounts.  In short, it costs MSFT next to nothing to make these monthly deposits.  No human is directly involved.  But MSFT wants your $200 for some reason, and you can’t have it, unless your sales allow your portion to amount to more than that.  Good luck with that, given the other support problems and the 20-item search result limit.
    I would think Microsoft’s war chest at this point has the funds available for someone (possibly named Steve) to dip into it and purchase a clue.  Their lack of real commitment to supporting app developers will only hurt MSFT and its customers, since these maladies almost ensure the continuance of a relatively low number of really great apps being available for the Windows 7 Phone. 
    Just some thoughts … maybe someone else needs to have more of their own thinking, too.  (Are you listening, Steve?  Can you hear the elephant breathing and scratching on the door?)

  • http://www.videoconverterfactory.com/tips/ Skyman

    windows phones?
    why Nokia choose Android?

  • http://www.articlespeak.com/overstock-coupons-overstock-promo-code-overstock-coupon-code/ Jasonvuhaight

    I got several notions from overstock coupon code forums. Overstock coupon code is too huge to get caught up by that. It will be detailed by them a while ago. I want you to follow it.
    http://www.articlespeak.com/overstock-coupons-overstock-promo-code-overstock-coupon-code/