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

  • quiksilvr - Tuesday, September 13, 2011 - link

    It makes no sense TO* have it Reply
  • Guspaz - Tuesday, September 13, 2011 - link

    Well, you can hit Win+D and get the traditional Windows UI... And that illusion of the familiar will last right up until you try to use the start menu to launch something, and get dumped back into Metro. It looks like there's no escaping it.

    My work machine has two 1280x1024 monitors. 23-point text on these things is going to be enormously huge, it's silly...
    Reply
  • alent1234 - Tuesday, September 13, 2011 - link

    because most servers have very few applications on them and it's dumb to hide them in the start menu. with the annoying mouse control of KVM switches this may make things a lot easier by using the wasted desktop space Reply
  • HMTK - Tuesday, September 13, 2011 - link

    I'm pretty sure they'll include it as a Feature on Windows 8 Server for one very good reason: RDS/Citrix. Reply
  • damianrobertjones - Tuesday, September 13, 2011 - link

    The users in work will absolutely LOVE this as they prefer things to be EASY TO USE Reply
  • Ratman6161 - Tuesday, September 13, 2011 - link

    At work, for our end users, it is all about the 2 or 3 business applications they use. Go from XP=>Vista=>7=>8 and those couple of apps have not changed. What is so hard about clicking the icon to start the program that they need a big box on their desktop to click on instead of the old style icon. What is to be gained? How is this more EASY TO USE for this group of people? Reply
  • UMADBRO - Tuesday, September 13, 2011 - link

    How is it not? Reply
  • Wraith404 - Thursday, September 15, 2011 - link

    Users at work won't ever see it, any self respecting system administrator will disable this Metro garbage in group policies. Reply
  • robinthakur - Wednesday, September 14, 2011 - link

    Agreed, Windows 7 phone could have been a contender, but everyone MS shopped it to at my old work (who already had iPhones) said it looked far too consumery and passed on the purchase. This is ironic because it integrated perfectly with our SharePoint architecture. They need to have a more corporate version...although I greatly suspect that it's too litle too late. Reply
  • cldudley - Thursday, September 15, 2011 - link

    They all have iPhones, and THIS is too consumer-y? Reply

Log in

Don't have an account? Sign up now