Redmond Diary

By Andrew J. Brust

Blog archive

WinMo's Demise: Notifying Next of "Kin"

This past Monday, April 12th, Visual Studio 2010 was launched. And on that same day, Microsoft also launched a new line of mobile phone handsets, called Kin. The two product launches are actually connected, but only by what they do not have in common, and what they commonly lack.

On the former point: VS 2010 had released to manufacturing a couple weeks prior to its launch. The Kin phones, meanwhile, are not yet available. We don't even know what they will cost. (And I think cost will be a major factor in Kin's success... I told ChannelWeb's Yara Souza so in this article.)

What do the two products both lack? Simple: Windows Mobile 6.x. For example, Kin seems to be based on the same platform as Windows Phone 7 (albeit a subset). And VS 2010 does not support .NET Compact Framework development, which means no .NET development support for WinMo 6.x and earlier.

So I guess April 12th marks Windows Phone "clean slate day." If you want to develop for the old phone platform, you will need to use the old version of Visual Studio (i.e. 2008). Luckily VS 2010 and 2008 can be installed side-by-side. But I doubt that's much consolation to developers who still target WinMo 6.5 and earlier.

Remember, WinMo isn't just about the phone. There are all sorts of non-telephony mobile devices, including ruggedized Pocket PC-style instruments, bar code readers and shop-floor-deployed units that don't run Windows Phone 7 and couldn't, even if they wanted to.

Where will developers in these markets go? I would guess some will stick with WinMo 6.x and earlier, until Windows Phone 7 can handle their workloads, assuming that does indeed happen. Others will likely go to Google's Android platform.

For OEMs and developers who need a customizable mobile software stack, Android is turning out to be out-WinMo-ing WinMo. As I wrote in this post, Google took Microsoft's model (minus the licensing fees) and combined it with a modern SmartPhone feature set (rather than a late 90s/early oughts PDA paradigm), to great success. You might say Google embraced and extended.

You might also say Microsoft shunned and withdrew

.

Posted by Andrew J. Brust on 04/19/2010


comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube