Developing For Metro – WinRT: The Metro API

So far we’ve talked about Metro from the end-user perspective where indeed it is a style and a UI. But Metro isn’t a way to display existing Windows application, it’s what results from a new development model for writing applications. Metro, as the user sees it, is the result of the APIs and design guidelines developers follow in creating Metro applications.

With Windows 8 Microsoft will be introducing a new API: Windows RunTime (WinRT). Over the years much has been said about replacing Microsoft’s long-lived Win32 API, with some success. The .Net Framework supersedes Win32 to some extent, but at the end of the day Win32 is still significantly used in one way or another by many developers. WinRT is the API that will replace Win32 for application developers, and is the API developers will need to use to develop for Metro.

WinRT in a nutshell is a combination of the elements needed to make Metro work, along with subsets of features from Win32, COM, .Net, and HTML5/CSS3. As with pure .Net applications, WinRT applications are meant to be architecture agnostic, and ideally Microsoft would like developers writing applications in runtime or interpreted languages such as C#, VB, HTML5/CSS/JavaScript, and even Silverlight. C and C++ will be able to access Metro too, although there’s still some ambiguity about under which conditions those will be architecture agnostic. In any case WinRT – and thereby Metro – will be accessible from virtually every language Microsoft supports today in their Visual Studio IDE. And regardless of the underlying language, all Metro applications will behave like first-class applications.

With all of this talk about WinRT, Microsoft went through great lengths to reiterate that developers will continue to have access to older APIs for new applications and that Windows 8 will run everything that Windows 7 can run. This is both because traditional/desktop styled applications will not be going away any time soon, and because WinRT as it stands is for user-facing applications, not device drivers, services, or other backend code. In fact desktop applications will be supported indefinitely (look at how long support for 16bit Windows applications has continued to last), but Microsoft clearly wants developers developing for Metro whenever possible, and not for the desktop. For a great many applications this makes sense, but I’m not sure anyone really understands what this means for specialty applications like 3dsMax, Adobe Photoshop, and other workhorses that not only have large legacy codebases, but whose usage model doesn’t easily flow with Metro.

 To entice application developers to use WinRT and Metro, Microsoft will be using a carrot and a stick. The carrot will be the Windows Store, the stick is that non-Metro APIs will not be available for ARM. ARM is Metro-only from day one, and the Windows Store will be the enforcer (more on that later). So if developers wish to target both ARM and x86/x64 users, they will need to develop Metro applications.

Developers working with Metro will be using Microsoft Visual Studio 2011, which like Windows 8 is in development and will be the first version of Visual Studio to support Metro. We won’t spend too much time on Visual Studio, but it will provide development facilities for all of the languages Metro supports, including HTML/CSS/JavaScript. For UI programming Microsoft’s Expression Blend 5 will play a big part, as XAML will be the UI markup language for most of the languages excluding HTML5/CSS.

The hard sell for Microsoft will begin tomorrow when the developers arrive. It’s clear that Microsoft has attempted to structure WinRT to be familiar to existing Windows programmers, but developers are just as sheepish (if not more) than end-users when it comes to change. It will also be the beginning of the process where the development community figures out where desktop applications fit in amongst the new Metro order. Even if Microsoft can sell developers on Metro from day one, there’s still a massive army of legacy machines – everything currently running Windows – that need to be factored in.

Mobile Experience, IE10, Live Cloud, Samsung Developer Preview PC The Windows Store
POST A COMMENT

235 Comments

View All Comments

  • A5 - Tuesday, September 13, 2011 - link

    They don't even bother to C&D the people who make explicitly LCARS skins for Android, so they would lose horribly if they tried to sue MS. You have to consistently defend your IP to keep it. Reply
  • UMADBRO - Tuesday, September 13, 2011 - link

    What are you smoking, and why arent you sharing? Reply
  • damianrobertjones - Tuesday, September 13, 2011 - link

    "The converse of that is that Metro feels akward and out of place when used with a mouse and keyboard as a laptop/desktop. "

    tell that to a new user who's using a computer for the first time.. they'll love it
    Reply
  • MacTheSpoon - Tuesday, September 13, 2011 - link

    Hmm... well, it is just a pre-beta. I'll keep my fingers crossed that it gets the kinks worked out. Reply
  • araczynski - Tuesday, September 13, 2011 - link

    ...bad enough pc games get basterdized console versions, now they're making their main OS consolized too...

    if this is their new norm, i'm just switching to apple, at least their crap is more stable.
    Reply
  • sviola - Tuesday, September 13, 2011 - link

    Then you're also going to be disappointed. THey seem to be moving OS X in the direction of iOS. But you can always install FreeBSD and run prompt only... Reply
  • damianrobertjones - Tuesday, September 13, 2011 - link

    Windows Media center was out before the Xbox and that used nearly the same look. Reply
  • Wellsoul2 - Thursday, September 15, 2011 - link

    "Windows Media center was out before the Xbox and that used nearly the same look. "

    I agree. It's very similar to WMC which makes it usable on my TV with a remote control.

    Sure it's dumbed down and clunky. WMC is very clunky IMHO.

    I really like the idea of using this OS with my HTPC though since it will make it
    easier to use all my programs with a remote control. The article didn't address
    that but the future may also be using your computer hooked to a TV alot of the time.
    For that purpose this is a good beginning.

    I'd be totally happy if I could switch between Metro and Win 7 desktop for the higher
    resolution desktop.
    Reply
  • ph0tek - Wednesday, September 14, 2011 - link

    Apple will do the same eventually. Only difference is Apple will pretend they did it first, as usual.

    Adapt or die.
    Reply
  • Dug - Tuesday, September 13, 2011 - link


    Business users want something like this. Portable, lightweight, easy to use.
    If they can have a full os and run the many apps they are used to without using a dumbed down version like on other tablets, it will be very well received.

    Look how hard companies try to make business apps on an ipad and android platforms. And how many people are using them but wish it to function like a full blown os.

    With this you get the best of both worlds.
    Plus you can easily use a mouse and keyboard when needed. You can't do that on android and ios because there is no mouse cursor.
    Reply

Log in

Don't have an account? Sign up now