This is a shout-out to all Zune 30 owners who remained patient.

This is to you, the faithful owner of a Zune 30, who didn’t buckle under stress and kept a keen eye on Microsoft, waiting for a solution.

This is to you, the discount shopper who picked up a Zune 30 and didn’t want to lose faith in your hardware.

Low and behold, Microsoft dug deep to find out the problem and, within minutes of finding out exactly what it was, pushed out an answer and a solution that didn’t void your warranty (thanks, Gizmodo). There’s a reason for why I’m bringing all of this up. July of 2008 saw cataclysmic server failure when a vast majority of all newly-purchased iPhone 3G units tried activating at nearly the same time, leaving both new iPhone 3Gs and some iPhone Gen 1 units dead in the water until the activation servers came back online. Poor planning led to the creation of a load-intolerant system on AT&T’s side (though the blame hardly belongs to them, given that Apple mandated this system in the first place). However, people weren’t infuriated by Apple’s ineptitude here. They were complacent and merely went with whatever explanation was fed to them. Meanwhile, a sizable majority of people who stuck with their own platforms of choice decided not to point and jeer.

Fast forward to December 31, 2008, and every Zune 30 device freezes due to a bug in a driver from Freescale Semiconductor in this while loop (between lines 259 and 274):

    while (days > 365)
    {
        if (IsLeapYear(year))
        {
            if (days > 366)
            {
                days -= 366;
                year += 1;
            }
        }
        else
        {
            days -= 365;
            year += 1;
        }
    }

(protip: day 366 triggers an infinite loop. To see the context of the code, check out the pastie link above, or just click here. You can see a breakdown of how this could’ve been handled here) 

What happened? Every Apple-loyal iPhone, iPod, and Mac owner threw a fit even though none of them actually owned a Zune 30 (You can’t run a Zune 30… or any Zune, for that matter, on a Mac). Thanks in part to the additional sensationalism promoted by gadget bloggers and, subsequently, news outlets the world over, a problem with a Zune model sold only in North America suddenly became a "Worldwide Zune Outage."

This is the difference between the Social and the Kingdom of Apple. Those with Zunes held out patiently and were rewarded with verbose output by Microsoft, whereas Apple simply vaguely alluded to some other company being the source of their problems (or were otherwise mute for a long period of time) whenever something on Apple’s side went wrong.

Thank you, Zune 30 owners, for living up to the hype of the Social. I’m now quite proud to be an owner of a Zune myself.

Wired has an interesting article on how the iPhone boosted smartphone sales for other manufacturers (most notably RIM and Palm). With the next version of the iPhone now released, you might be asking yourself

• What will Microsoft do to keep Apple from breaking into the enterprise smartphone market?
• Why haven’t I bought this new iPhone yet?
• What’s that pretty thing in the Crystal Ball?

Now might be a good time to analyze the potential impact Apple’s iPhone might have on Windows Mobile.

The current version of Windows Mobile is version 6.1… which is still based on Windows CE 5.2 despite the release of Windows CE 6.0 back in November of 2006, which is well over a year ago. Windows Mobile 7 will be based on either Windows CE 6 or a later version of Windows CE judging by its anticipated mid-to-late 2009 release. Since the last major Windows CE release, two iPhones have come along and, according to the people watching today’s WWDC keynote, eclipsed every smartphone in existence (we’ll disregard the argument that the iPhone is not a suitable enterprise tool for now).

Since the moment news of the first iPhone broke two Januarys ago, companies such as Meizu and HTC have tried to revamp the Windows Mobile interface with their own code, though only HTC has actually managed to push anything to the market. A number of threads discussing the new HTC Touch Pro have come and gone, with many people as-yet-unaffected by Mr. Jobs’ Reality Distortion Field seriously weighing the unreleased Touch (less so with its Diamond sibling) against the new iPhone and another HTC project, the Sony Ericsson XPERIA X1.

The impact of the iPhone is already visible in the preparation of new user interfaces for both Windows Mobile and RIM’s Blackberry (the Bold UI). However, with the announcement that iPhone v2 will carry full Exchange support, the latest iPhone is also making an attempt to invade the enterprise smartphone realm, and third party innovations for smartphones in this department typically have a high FAIL rate in catching on, so it’s up to Microsoft to keep itself awake and running. HTC pulled a lucky rabbit from its proverbial top-hat, but HTC’s experience lies in what most people in the Orient prefer with their phones: glitz, glamour, and lots of overly pretty animated functions, menus, spinning icons, and other similar user interface clutterings enhancements which missed the Longhorn boat back in 2004.

This gets me to what I think Microsoft might be forced to do with Apple’s growling 2ft-tall-and-growing-fast presence in front of it.

Background Applications won’t go away. Even though Apple had a fun jab at how background applications eat battery power and performance, I personally don’t believe Microsoft will let background applications go the way of the dodo. Instead, Microsoft will likely make enhancements to how Windows Mobile manages background applications. This will save battery power (good!) while making it less likely that your phone will be infected with spyware (good!), while also preserving backwards compatibility (good, but not as enthusiastically good).

A revamped user interface will likely be issued with Windows Mobile 7. While this has already been discussed many times in the past, I personally think the new UI will be developed in tandem with Windows 7’s User Interface. We’ve seen Windows 7’s poorly executed touch demo at D6 (I’ll keep my 50 cents Steve, thank you), but I think that Microsoft will keep a similar but highly condensed touch-centric user experience for Windows Mobile 7 for two reasons:

1. The iPhone has already made touch look cool, and with companies such as HTC pulling off some of the most ingenious touch interfaces , touch and gestures won’t be going away.
2. Microsoft has a history of keeping things looking alike (and yet disjointedly different at the same time) for the sake of branding. Windows Mobile 6 had this mildly Vista-esque feel through the use of gradients and glossed elements. On the other hand, this is a phone. One of the problems some people have with the iPhone is that while the user interface is great, the time it takes to go from one place to another (despite the presence of the home button) can get a bit annoying with the animations and other UI tidbits in place. In consumer environments, a glitzy UI is great, but in snappy business environments when CEOs are jumping from cabs and limousines to business meetings in skyscrapers while trying to arrange that multi-million (or billion) dollar merger during the only 30 second time slot available in the elevator trip to the top floor, the last thing that is needed are animations which eat time.

With that in mind, Windows 7 might be less of a festival of motion than Windows Mobile 6.1 with HTC’s TouchFLO, with a new interface likely catering to both businessmen and consumers alike.

Accelerated Development might split priority between Windows 7 and Windows Mobile 7. Should the two systems share a similar user interface, seeing Microsoft split its resources down the middle for both Windows and Windows Mobile might not be the largest surprise. One of Microsoft’s most successful areas is within the corporate sector, and with the iPhone trying to barge in, Microsoft might be much more inclined than before to put more emphasis on Windows Mobile development. With connectivity becoming the ultimate focus for Windows 7, seeing a heavy emphasis on connectivity between Windows Mobile, 7 and Windows 7 might be less of a shock now than it might’ve been, say, three to six months ago. This doesn’t mean we’ll see Windows 7 launch in 2009, nor does it mean that Windows 7 will come before the second half of next year (but it might). All it means is that more teams might be devoted to Windows Mobile 7, with collaboration between both Windows and Windows Mobile development climbing much higher than ever before. This could also mean that a number of Microsoft’s Windows 7 “pillars” will carry over into Windows Mobile.

Mind you, all of this is my own mindless speculation. The iPhone is not a crystal ball, I can’t see into the future, and the phone in the ball is an HTC Touch Pro. If you have any other ideas as to which directions Microsoft might take with Windows Mobile, post! Comments are below, but before you post, here’s a dose of irony, courtesy of Paul Thurrott.