Onward and Upward

Blog archive

Microsoft's Branding Nightmare

Metro? Modern? Windows 8? What's going on here?

First, word comes that Metro's out as a designation meaning "applications built for the version of Windows 8 that runs on ARM processors". Apparently, there was a partner conflict that Microsoft didn't want to turn ugly. But here's the thing: Metro's been used for years now to refer to the new UI. My question: why didn't anyone discover this potential conflict before? Big, huge, Jupiter-sized epic fail by marketing or someone else at Microsoft. My prediction: heads, more than one, are going to roll over this -- in fact, they may have already.

Since the initial revelation that Metro's gone, several more trial balloons have been floated. The first was simply replacing Metro with "Windows 8". That's a tough one, however, since Windows 8 is an operating system, and not a UI. Can you see the potential confusion coming? Windows 8 apps on Windows 9? Windows 10? One shudders at the thought.

The latest rumors floating around the Web, from Mary Jo Foley and others, is that "Windows 8" may be out, and "Modern" may be in as the UI designation. This makes more sense, since it would once again be referring specifically to a UI, and not an OS. I have to say, however, that Modern doesn't exactly thrill my toes as a name. Sorta bland, blah, un-memorable.

I wouldn't be surprised if Microsoft's not done. It seems the company isn't sure what to do now, so they're flailing about, throwing name spaghetti at the wall and seeing what's likely to stick. Given the name-game musical chairs now being played, it seems that this is a pretty big deal in Redmond. And indeed, it should be. Windows 8 is a critical product, acting as the first bridge between the traditional software/OS combo and the mobile era that demands new software and nimble OSes. Getting the branding right is important, since those products will be competing with the dominant brands of Apple and Android.

In other words, I'd be surprised if the name ends up being Modern or Windows 8. This may not be settled until Build.

Posted by Keith Ward on 08/10/2012


comments powered by Disqus

Featured

  • Mastering Blazor Authentication and Authorization

    At the Visual Studio Live! @ Microsoft HQ developer conference set for August, Rockford Lhotka will explain the ins and outs of authentication across Blazor Server, WebAssembly, and .NET MAUI Hybrid apps, and show how to use identity and claims to customize application behavior through fine-grained authorization.

  • Linear Support Vector Regression from Scratch Using C# with Evolutionary Training

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the linear support vector regression (linear SVR) technique, where the goal is to predict a single numeric value. A linear SVR model uses an unusual error/loss function and cannot be trained using standard simple techniques, and so evolutionary optimization training is used.

  • Low-Code Report Says AI Will Enhance, Not Replace DIY Dev Tools

    Along with replacing software developers and possibly killing humanity, advanced AI is seen by many as a death knell for the do-it-yourself, low-code/no-code tooling industry, but a new report belies that notion.

  • Vibe Coding with Latest Visual Studio Preview

    Microsoft's latest Visual Studio preview facilitates "vibe coding," where developers mainly use GitHub Copilot AI to do all the programming in accordance with spoken or typed instructions.

  • Steve Sanderson Previews AI App Dev: Small Models, Agents and a Blazor Voice Assistant

    Blazor creator Steve Sanderson presented a keynote at the recent NDC London 2025 conference where he previewed the future of .NET application development with smaller AI models and autonomous agents, along with showcasing a new Blazor voice assistant project demonstrating cutting-edge functionality.

Subscribe on YouTube