29
Dec 12

When I worked at Microsoft

Few phrases would strike fear into the hearts of my co-workers in Austin faster than “when I worked at Microsoft”. I’ve since learned to keep my stories to myself a bit more. But recently I’ve been contemplating not what I learned at Microsoft, but instead what I’ve learned since.

At Microsoft, I was a horrible writer. I’ll be honest. I hated writing specs. Considering I was a Program Manager (PM), I think that was a bad thing (in hindsight). But I’ve realized since then that it wasn’t the writing that I hated, it was the process. I lucked out and worked with several devs for most of my career in Windows that were willing to work “on the fly” on features as we isolated the customer need. In particular, one dev and I did an immense amount of work on a key deployment feature primarily using his whiteboard and my whiteboard.

In particular, I hated the idea of creating a monolithic document that was often referred to as an “artifact”. Artifacts aren’t things that people use. Artifacts are something that archaeologists discover after great societies fail.

In 2005, while I worked at Winternals, I was offered an opportunity to write an article for TechNet Magazine. One article became 3, 3 articles became a year-long contract, and that was renewed. For many of these pieces, I largely just regurgitated knowledge about how deployment features worked based upon my deep knowledge of them. I built a quickie outline, filled it in with knowledge, made a few edit passes, and handed it off. For better or worse, most of my pieces went to publish with only a quick edit after that.

A few years later, as TechNet changed forms, my contract wasn’t renewed. For a while I wasn’t writing. In 2010 I joined Directions on Microsoft, who I had met in 2001 when describing a feature that I owned to my now colleague Michael.

Directions has a guiding tenet – the idea of uncovering the fundamental news for whatever topic you’re writing about. You have the obligation, as a writer, to describe to your reader what the feature or technology is, how it works, and how it could prove valuable to the reader (or what gotchas it brings). Many of us are ex-Microsoft, and understand the importance of approaching the idea of describing the technology not necessarily in terms of the marketing message, but instead in terms of the actual value customers can expect to find in the technology, or the complications that they may find as well.

The hardest part of becoming an effective analyst at Directions in fact has less to do with understanding how the technology you are covering works, and more with how to adequately, and accurately describe it to the reader, without overwhelming them. In short, like many kinds of sauces or foods, it’s not throwing things together quickly and eating. It’s a matter of finding the important elements, making an outline, reducing it to the important key components, and writing an effective piece. Sometimes this process takes days. sometimes it takes weeks. Sometimes you have to go through the process of letting go after you realize that there is no story there. Then several comprehensive edits later, ideally, you have a piece you can be proud of.

In this video, one of my favorites on YouTube, Apple designer Jony Ive discusses Apple’s approach to design, and in many ways, towards manufacturing. I’ve watched this many times, and what I take away from it is that good technology is complicated, and good designers do their best to buffer the end user from that complexity. Either a good designer absorbs the complexity of the technology and makes the experience approachable for the user, or a bad designer fails, and passes along the complexity of the underlying technology to the user - producing technology that is unpleasant to use, and often largely unusable.

As I read a lot of content on the Web, sometimes it drives me a bit crazy. So many articles - like my old ones at TechNet were at times - aren’t planned well, aren’t edited, ramble on, leave key points unclosed while  wasting time on chaff. All too often I click through to an article – or often a blog post – and abandon it at the 1,000 word mark, when it appears sufficiently clear that the writer lost their way in the woods, and at some point simply said, “screw it, I’m done”, and pushed publish, when they should have either saved it as a draft or just closed their browser.

Earlier tonight, I stated on Twitter that I think many of the things I’ve learned that have made me a better writer today would helped me a better PM at Microsoft. In addition to writing and editing skills, part of this is likely my own maturity, and another part is surely me having the patience to do the best job possible and taking my time to do it - even if it means cutting key work I’ve done, or discarding an idea that is important to me personally. Finally, another part I’ve learned is that it’s okay to write with brevity – as I always wanted to do at Microsoft – as long as you manage to clearly and accurately get the primary points across to the reader - at Microsoft, the developers, testers, user assistance writers, among others. Whether you’re a PM at Microsoft, a writer, or a blogger, I think it’s important to understand who your consumer is, what you’re trying to tell them, and if you’ve successfully transmitted your message, or whether you’ve gotten lost along the way.


20
Dec 12

All I want for Christmas – my Windows v.Next wishlist

For almost two weeks, my main computer – a ThinkPad W510 (circa 2010) has been running Windows 8. Courtesy of the Logitech Touchpad T650 I’ve mentioned here and many times on Twitter, the experience has been – to me – much smoother than when I was trying to use Windows 8 (in a VM, admittedly) with a mouse during the previews.

Three things I want to say up front:

  1. I’m trying to be positive and fair, and give Windows 8 on a touchless system a shot.
  2. I’m writing this from the perspective of a person with a laptop (docked or other), or a desktop, without touch. Because that’s what I have and what I use most of the time – and for the next several years or more, that’s not a freakishly uncommon scenario.
  3. I’m almost not going to talk about apps at all. For a change. I have several installed, I’ll talk in a few weeks about the ones I really find myself using.

No, instead, I’ve got a wish list. It’s not quite Christmas, but I don’t think Microsoft can get me these this year. So perhaps over the next year?

In no particular order:

  1. Add back key system state to the Start screen (clock/battery/wireless). These three intrinsics are there on the desktop taskbar. They’re even there when you power on your Windows 8/RT device before the logon screen. They’re even visible on iOS (sorry – first of three times I’ll do this) with most applications, unless the application elects to hide the status bar. So why are they missing on the Start screen and while running applications? Hiding chrome is good. But you can go too far, and I think the loss of these three items exemplifies this. There are three important things to know on a computer – even a fruit-flavored one that fits in your pocket – 1) What time is it, 2) Am I connected to a network, and 3) When will this thing run out of juice. Don’t be shy about sharing that info with the users. I’m currently using Ze Clock to show a tile that displays date and time, but this is duct tape and should be in the OS – especially when I’m in an app.
  2. Add back a visual cue of some type for mouse users to indicate where to navigate to for the Start screen. If you’re using a tablet, you’ve got the Windows key front and center (literally). With my Logitech, I’ve got an easy gesture (three fingers up) to navigate to it. Yes, I know there is a button on the keyboard to open it. But users have been trained for 17 years to click a button with a mouse to launch apps – and the entire visual cue just disappeared, unless you hover over it. Proper behavior in my opinon? Show the start orb (even a sexy new one for Windows 8+) that pops the Start screen open. it’s okay that it opens the Start screen. But you’ve fundamentally disconnected the trigger that users on a desktop expect, and that novice users search for. When you find that the system supports touch, hide the orb. That, to me, is the best of all worlds.
  3. Add the Search charm functionality to the desktop through an Explorer band. Heck, you might even be able to skip item 1 if you do this. Equivalent to the old URL band in Explorer. I just wish without touch there was a single-step way to invoke the Search charm because it works really, really well.
  4. When you open the Charm bar – type ahead should automatically start searching. When you are on the Start screen, just typing begins invoking the Search charm and showing results. When you flick open the Charm bar, the same thing should happen. The Charm bar moves to the top of the Z-order, but it isn’t doing anything until you choose a charm. If the user just begins typing after they open it, I think it’s safe to assume they want to search. Can you tell I like the Search charm?
  5. Add intrinsic social sharing. On iOS (sorry – but hey, it’s only the second time I’ve invoked it, right?), it’s remarkably easy to share from iOS to Twitter, and now to Facebook – through the OS. When you want to share a URL from IE, in particular, this is remarkably hard. Even if Microsoft doesn’t want to build apps for Twitter or Facebook, I think building in first-class sharing to share links to Twitter, Facebook (and LinkedIn if you’d like, though I could care less) directly from the browser would be wonderful. Huge favor – do what Buffer does, and grab the title AND the URL automatically. I was originally going to suggest that IE needs some sort of new extensibility model that would work on Windows RT as well, but to me, this is really what I need that IE (especially immersive IE) is missing.
  6. Fix Favorites. Even when I worked at Microsoft years ago and advocated roaming favorites (1999, baby!) it seemed like Favorites were the cobbler’s child of IE. I get that in many ways the “Frequent” screen shown when you open a new tab has replaced them. But it isn’t the same. In both immersive and desktop IE, Favorites are all but dead… Tucked away in a shoebox like photos from 1978. You put all this love into the Start screen – how about something Start screen-like for Favorites in IE? There has to be something that can be done here, it’s just sort of broken and lost right now. No, pinning pages to the Start screen doesn’t count. That’s nuts. Semantic zoom or not, the human brain can only take so much load – plus, there’s no way to pin Favorites that I specifically want to launch desktop IE.
  7. Fix Internet Explorer modes. Explaining the modes in a modeless operating system is becoming challenging for me. Sorry, if you don’t like hearing that Windows 8 has modes, skip to my next wish. Windows 8 vs. Windows RT; immersive vs. desktop; immersive IE vs  desktop IE. Frankly, I don’t even get why there really are two modes of IE. You should really either detect touch and go all-in with immersive, or let the user select and have a default. I find that I use desktop mode far more in my scenario, and immersive is just frustrating to use on a system without touch. Third and final time I’ll invoke iOS here. On the iPhone, Safari hides the browser and goes completely “immersive” all the time. There are no cues to get it to open up again, but it’s there, and you learn what to tap. On the iPad, Safari always has the address bar and list of tabs visible, and has an option to show bookmarks as well. I get that chromeless browsing is the new teh sexy. But this is baby with bathwater stuff. It’s a pain to switch tabs. It’s a pain to open Favorites. It’s a pain to even open a new URL, especially without touch. This is one of the principal reasons I use desktop, not immersive, IE. Some chrome is okay. Really. Users will thank you for it.
  8. Let me pin Desktop IE to the Start screen. If you’re not going to make immersive IE less… well… immersive, let me pin an icon for Desktop IE on the Start screen. Believe it or not, that is the only remaining icon pinned on my taskbar now – because I do need it – but as far as I can find, there is no way to pin it to the Start screen. Add that and I’m all in on the Start screen. Seriously. All. In.
  9. Copy/Paste for WinRT Remote Desktop app. One of the most beautiful features ever added to RDP in Win32. Works on my Mac’s RDP client. I really wish it worked from the WinRT RDP client as well.
  10. Win32 Share charm integration. There’s an icky disconnect between Win32 apps and WinRT apps. You can’t readily share back and forth. Either the clipboard needs to be extended into and out of the Share charm, or Win32 apps (I’m looking at you, Office 2013) should get the ability to implement Share contracts in particular. Try getting a JPG file out of SkyDrive on Windows RT and pasting it into Word. It’s not pretty. As with the previous item, it’d be ideal if you could move files back and forth from WinRT to Win32 and back more readily. I get it’s V1, and this creates a security and workflow issue. But it needs to be solved, as it’s a fundamental disconnect on WinRT.
  11. Taskbar group. Especially on systems without touch that are upgraded from a previous version of Windows, create a group of items in the Start screen that is an exact mirror of the Taskbar, called “Taskbar applications” or the like. I did this myself, manually, and it really makes the transition to using the Start screen less foreboding.
  12. Startup group. I like to have Outlook start when I log on. I use it all the time. There should be a way to do this without doing that, and the somewhat cumbersome startup tools in Task Manager don’t let you add easily, nor should that be the way to do this. Perhaps add an option on the right-click menu for an app to Add it/Remove it, respectively, from the user’s Startup? Right-click, “Run this program when I log on” or ”Don’t run this program when I log on”.
  13. Make (re)naming a Start screen group easier. If I right-click above a group of tiles in the Start screen, semantic zoom out, and pop up the dialog for (re)name. This easily isn’t easily discovered as it exists today.
  14. Sync my apps/Start screen. Easy, right? Not so much, and I get that. But this is huge. Once you use Office 2013 with SkyDrive or SkyDrive Pro, you realize how awesome deep sync integration is. But this is a bit of a weird hole in Windows 8/RT. All of the advertising for Windows Phone 8 in particular talks about how you can make it yours… so as a user, you spend all this time tweaking your Start screen on Windows 8. Then you get a Windows RT device to test with. And you have to manually sync your apps (the Windows Store could do better here) and then recompose your Start screen. Get a replacement device? Do it again. I have ideas on how this could work that would be elegant - but I really think this has to happen.
  15. Don’t hide shutdown. One of the devs I worked with at Microsoft used to have this book on his bookshelf at the office. Much like that topic, it’s something most of us would rather not talk about, but the truth is, shutdown happens. Everything else under the main Settings charm is indeed a setting. But power isn’t a setting. It’s a state. Moreover, it’s not that different from the logged out or locked states that are already present under the user’s tile on the Start screen. Whether on a machine with touch or not, there should be a more discoverable way to reboot the device. It’s a fact of life that once a month you need to reboot a Windows PC, minimum (usually a bit more). It shouldn’t be this hard to do.
  16. Finish off the Control Panel. It’s a weird parallel universe – this setting is over there, this one is over here. Running Windows Update from here doesn’t always work, but from over there, it does. Ideally, the Control Panel should be nuked from orbit, except as it must be kept around for legacy/third-party CPLs that can’t run in the new world.

So there it is. Nothing too harsh, but I’m still primarily a desktop guy at this point. We’ll see what wishes I come up with as I spend more time in immersive land.


10
Dec 12

100 Days – On Twitter and the virality of exclusive information.

Early Aug. 2012 - Short of information about how the Windows Store, the forthcoming home for Windows Store (nee Metro) applications was doing, I began exploring the store, trying to assess how many applications were actually there. I had heard rumblings of 400 or so applications. As I said late in Sept. 2012, my intentions were never malicious. I pondered whether there was any way to query the store programmatically. Here’s how it went down.

Aug. 15, 2012 – I had discussed an idea with a friend on how to query the Windows Store, and tried it. My initial results, after fiddling with my idea for a bit, resulted in a count of 534 applications available worldwide.

Aug. 28, 2012 – I registered winappupdate.com and created the Twitter account @WinAppUpdate, but let them sit dormant for a while.

I was still only polling the store on occasion. On Sept. 5, 2012, I saw the store pass 1,000 applications worldwide – on Sept. 10, 2011 I began polling it every day, and we posted a State of the Store article at Directions that sought to more broadly discuss the composition of the store, not just the count.

Sept. 16, 2012 – I posted the first blog post on WinAppUpdate.com, announcing that there were 1,749 applications worldwide, and linked to it from Twitter. I added myself and a few other people, but effectively I had no followers. As someone with a psychology and sociology background, the virality with which the statistics spread and followers of the Twitter account for @WinAppUpdate grew, I found it fascinating, and I was glad that people found the information and the numbers interesting and helpful.

Over the next two weeks, as Mary Jo Foley, Alex Wilhelm, and Charlie Kindel, among others, mentioned this site, my stats, and the Twitter account, it began to grow in followers significantly. I can tell you from having had it happen on getwired.com before, you do not want to get sent Mary Jo’s traffic when you are not ready. It does unpleasant things to your site.

Throughout September and October of 2012, stats that I posted on Twitter resonated pretty well, and the @WinAppUpdate account began to grow in followers. Anytime Mary Jo or Alex would mention the Twitter account or the site, I would gain several – or many – followers. What I found most fascinating was how many of these followers were Microsoft employees or partners. There was a genuine scarcity of information around Windows 8 throughout the preview process and both employees and partners, among everyone else, seemed to want to know what was going on with the Windows Store. Over the next almost 3 months, the @WinAppUpdate account grew slowly at first, but then quite dramatically.

There were, for the next two and a half months, only two sources of application counts – my site and this site, where he has diligently counted the number of apps using a different approach than me, and at first I didn’t think his methodology would work – but I think it does, and lucky for him, it can continue where mine may have hit the end of the line.

Oct. 26, 2012 – Windows 8 RTM – I noted that the store was at 9,029 applications, and as media coverage of Windows 8 increased, so did discussions of my counts, and the number of followers. Conversations with Mary Jo and Alex on Twitter, as well as mentions of the Twitter account in the news media surely helped to keep the count of followers growing, even as I both diligently tried to stop making “the count” the focus of discussion – and in particular the discussion on my @WinAppUpdate account. On the same day, I also posted on getwired.com The Turn, where I more or less bared all about how I collected my statistics.

Throughout this exercise, as I said, my intent was never malicious. I knew at some point, Microsoft could - nay, should figure out how I was doing it, and either ask me to stop or simply shut off the spigot (easier said than done, as it could affect the SEO of the Windows Store). That said, I have always felt that if Microsoft asked me, I would have stopped counting or discussing the content on the store. I was providing the numbers, and then the deeper analysis, to help people understand what was going on in the store. I did announce when the store had hit 10,000, and 20,000, applications worldwide, and when there appeared to be more apps in the China Windows Store than the US Windows Store.

After I announced how I did my counts, as I somewhat anticipated, a few people started emulating.

Nov. 30, 2012 – I was about a group of guys who have built a Web-based front-end to the Windows Store, now at http://metrostore.preweb.sk/.

Over the next week, that site got some publicity. I continued to shift discussion away from counts both on my blog and @WinAppUpdate. Though that Web-based Windows Store now included a count, I only handed out a vague “over 25K” answer when asked during the week of Dec. 3, 2012. I had spent the last month really trying to find and discuss apps that I found significant, rather than discussing counts.

Early on, the script that ran my counter did its work in the morning. I shifted it to the nighttime – at about 10PM PST, when the time that Microsoft would push out their sitemaps seemed to have reliably occurred.

Dec. 5, 2012 – The last successful polling of the Windows Store occurred from my app.

Dec. 6, 2012 – I checked my stats in the evening before going to bed. My Excel spreadsheet, which has grown from several KB to more than 7MB, was completely empty, save my Excel formulas that I inserted at build. I checked the sitemaps manually. The first part was there, and pointed to the second. The second part was there, and pointed to the actual sitemaps. The actual sitemaps… were dead. Search engines that hit the site manually are going to be confused. But if Microsoft has elected to do this on purpose, then that meant they are likely submitting the sitemaps directly to Bing, Google, and Yahoo.

Dec. 12, 2012 – So here we are. It was 100 days since from the day I first created the @WinAppUpdate account and registered  the domain name to when I lost the ability to investigate the store. The Twitter account now has 1,378 followers, after only 831 tweets. That works out to 1.65 followers per tweet, or 16.65 followers per day. When you compare that to my original @Getwired account on Twitter, which I created on May 31, 2008, it’s pretty astonishing. After an insane number of tweets (59,518) and 1,653 days on Twitter, I have only 2,513 followers. With @Getwired, I’ve found that breaking the news – finding a news source before anyone else (or saying something genuinely, uniquely witty or thoughtful) – really does help generate new followers and create tweets that resonate. Though @WinAppUpdate did not generate a massive number of tweets, nor a massive amount that resonated widely on Twitter (I think 13 or 20 RTs of one was the largest I saw, and I’ve seen better than that on @Getwired), the number of followers, and followers who recommended the account to others, speaks highly of the value people find in Twitter when the information is truly unique, and can’t be found through any other source.

As for me, for now (for obvious reasons) I’m standing down on counting apps or mining the store. I can’t be certain whether I was the reason, or someone else was the reason, as to why the sitemaps went offline – or if they went offline by accident. @WinAppUpdate has been an amazing ride, and I’ve thoroughly enjoyed the conversations I’ve had around the Windows Store over the last several months. I’m leaving the app counting to those who have other means to count than my methodology, and leaving analysis of the contents and quality of Windows Store apps to those who have the time to do such an exercise justice – given the need to dig through the store to find them now, I don’t have the time to carry on with it.

I plan to retire the @WinAppUpdate Twitter account shortly. The blog URL will most likely redirect to this site, or perhaps a partner site if I can find a relevant one. All of the blog contents have been moved to Getwired.com for posterity, under the account  at WinAppUpdate. To my followers on Twitter – I thank you all for joining me on this wild and crazy ride, and hope you’ll join me at @getwired as well, where I’m really just getting started with Windows 8.


07
Dec 12

Review: Logitech Touchpad (T650)

If you’ve known me long, you’ve known that I’ve been far from Windows 8′s biggest fan. For me, that’s been for a specific reason. The concessions that Windows 8 makes to being touch focused have – I strongly believe – compromised the ability for those of us damned to the desktop to really use the platform.

While I believe Microsoft intends for Windows 8 to be a success both with tablets and on non-touch devices, learning to use the operating system if you have a “touchless” device as I do can be a chore. My main computer is a ThinkPad W510. A relatively beefy (read: horrible battery life) Intel i7 laptop, the W510 is, horsepower-wise, more than an optimal candidate for Windows 8. Though it doesn’t support UEFI, it ran preview versions of Windows 8 quite well, whether I was running Windows to Go from a USB Flash Drive, or using VMware Workstation to run it virtually on Windows 7.

But my ThinkPad, like almost all Lenovos on the market in 2010 (and many today) didn’t/doesn’t/won’t support touch. When mobile, it has a capable 15.6″ display, and at work I dock it and use my main monitor, a gorgeous 27″ Acer. Neither has touch, and with the distance between myself and the displays, my typical work layout would make me a good candidate for gorilla arm if I used touch all the time on either one:

While friends kept telling me, “just memorize the keyboard shortcuts“, I had to say, “no“. Perhaps it’s because I’m a visual/spatial person (a “colors” person as a colleague says), perhaps it’s the sheer frustration at needing to memorize keyboard shortcuts to do what I used to use a mouse for, I didn’t want to learn 20 keyboard shortcuts. A colleague pointed out how excited I was to learn 13 new gestures upon getting the Logitech, and I guess we’re both still befuddled at that.

I had heard from several people that had tried the Logitech T650 that they were very satisfied with how it worked for them. Having used MacBook Pros for 3+ of the years I worked in Austin, as well as using ThinkPads and Toshibas with decent trackpads (but nothing like Apple’s) and being a very happy user of the Apple Magic Trackpad at home on my iMac, I really wanted to try the Logitech and see how it worked together with Windows 8. Only problem? I couldn’t find one! My local Best Buy seemed to sell out as soon as it received a shipment. A local reseller was supposed to get some in late last week, but still hasn’t. I happened to be by Best Buy in Bellevue, WA on Wednesday evening and they had one left. One. As best I can tell, the device is selling incredibly well. Unfortunately when I tried searching a couple of retailers online, I didn’t even get out of stock notifications – just pages telling me that they no longer sold the HP TouchPad (unfortunate naming overlap).

I’ve had a few people ask me why I didn’t just use another Apple Magic Trackpad. Because Apple’s gesture support for Windows stinks. They could enable the same gestures for Windows as they do on the Mac, but it would take considerable work, and to what end? So only a fraction of the gestures enabled on the Mac work on Windows – and none of the ones that would make life with Windows 8 much more palatable without touch.

Touchpad in hand, with a freshly installed upgrade from Windows 7 Pro to Windows 8 Pro installed, I set forth to try it out. The device is packed in a box that is vaguely Apple-like. No foam, a bit of paperboard. No driver CD included. Comes with the Touchpad, wireless dongle, charging cable, and instructions/warranty info.

First impressions? The Touchpad is big. No, not as big as Logitech’s odd “Touchpad in Lilliput” images on their site may make you think. but it is significantly larger than the trackpad on my ThinkPad. Here is an actual picture of the T650.

The device is wireless and requires no batteries. Logitech claims roughly one month per charge, and mine came fully charged as best as I could tell. You can also use the device while it is charging, which is a nice touch.

Assuming mine was not charged, I plugged in the USB dongle (I wish it was just Bluetooth!), the cable to another USB port and the other end to the Touchpad. There is no software included, but upon plugging it in, it installed the Logitech receiver and prompted to download and install the Logitech SetPoint Software. It was a very smooth, consumer-friendly experience. My only frustration was trying to use the Logitech Unifying Software, which prompts you to power cycle the Touchpad in order to pair it. I was never able to satiate the software that it was paired, yet the Touchpad worked. Odd.

The SetPoint software is relatively well designed, and easily lets you tweak which gestures trigger left, right, or middle click. I configured mine to mimic Apple’s, which I’m used to. Single finger click for left click, double finger click for right click.

Most importantly, for a device with no physical (or on screen) Start button, getting back and forth from the Start Screen and desktop was most critical to me. For this, a three finger swipe up gets you to the Start Screen. Three fingers back down gets you to the desktop. Three fingers down again minimizes all desktop apps and shows you the actual desktop. Nice touch. Two fingers allows you to have a Mac-like smooth scrolling experience. While Tweetro+ was temperamental a bit with this scroll, tending to overscroll a bit, Word, IE, and Outlook seemed to work quite well with it. A three-fingered swipe back and forth functions as a back/forward button and was wonderful in IE in particular.

The commonplace two-finger pinch gesture enables you to zoom in or out in many applications – I did experience some frustration in getting WinRT-mode IE in particular to like this gesture. Scrolling and pinch and zoom didn’t seem to work in the Windows common control (File Open) dialogs, an unfortunate, but minor omission.

Swiping in from edges works as you’d expect, with the app switcher (left swipe in) and Charms (right swipe in). Theoretically the top and bottom edges also display the app bar as they would on a touchscreen. While it did work sometimes, I found it a bit more temperamental. My one wish for the device would be that in a future design, Logitech include a small (say, 1/4″) outside edge that can be felt, or perhaps a small indentation to place your finger on in order to start an “edge gesture”. I say this because in particular the gesture to trigger the Charms is hard to place correctly. You want to almost start with your finger partially off the right side of the device and swipe on, but that doesn’t work well. In testing, I eventually found that the device is somewhat tolerant of this, and you don’t have to have your finger truly on the edge in order to do an edge gesture. That said, having an actual edge or bevel might make this easier for novices to learn.

Finally, Logitech includes several 4-fingered gestures for dealing with the currently active desktop application. These mirror Windows Snap functionality and include four finger swipe up or down (maximize or minimize, respectively), and left or right (left or right-side Snap). Unfortunately, these gestures don’t work to snap Windows Store applications, nor am I sure Logitech could even enable that if they wanted to.

Like the Apple Magic Trackpad, the T650′s click is physical – and how well it works depends on the surface you use it on. On my wooden desk itself it worked flawlessly. On the 3M “Precise Mousing Surface” attached to my keyboard, which slightly wobbles? Not so well. I view this as more of a defect of my desk than the Touchpad, personally. All in all, the device is built quite well.

I think that while there may be a category of Windows Store apps that this device still won’t enable (games, drawing applications or other application best handled with actual direct touch), a broad swath of the Windows Store applications, and Windows 8 itself, become much more readily approachable with the T650 than I believe they do with a mouse. More importantly, the T650 allows you to interact well with Windows 8 while still interacting well with the desktop environs and desktop applications that many of us will still be using for quite some time.

Once you get adjusted to the gestures included in the Logitech T650, I firmly believe you’ll find that not only is it a thoughtfully designed device that complements Windows 8, it is a device that honestly lets Windows 8 shine on touchless devices much better than it (Windows 8) can on a device equipped solely with a mouse.

Device specifics:

  1. Interface: Proprietary wireless. Works with some other Logitech devices.
  2. Included: Touchpad, wireless dongle, charging cable, instructions/warranty info.
  3. Price as tested: $79.99 before tax. Available at some locations for slightly less.
  4. Dimensions (courtesy of Logitech):  Width: 134 mm / 5.3 in. Height: 8.7mm / 0.34 in. 12mm / 0.47 in. (USB cable plugged in) Length: 129 mm / 5.1 in.
  5. Wireless: 33-foot wireless range, 2.4 GHz (Logitech proprietary – not Bluetooth).
  6. Works with: Windows 8, Windows 7, Windows RT. I tested on Windows 8 – cannot speak to the experience with Windows RT.

Pros:

  1. Excellent gesture support, makes Windows 8 without touch habitable.
  2. Well-designed interface for tweaking actions for the built-in gestures.
  3. Phenomenally large trackpad surface.
  4. Cordless, yet rechargable through included USB cable, no batteries needed.
  5. Glass top makes it serve as an excellent coaster. I kid!

Cons:

  1. Not cheap.
  2. Requires proprietary Logitech USB dongle. Augh.
  3. Should have a bevel or edge to demarcate the outer edge for edge->in gestures.
  4. Pairing app didn’t work. But it paired. Very confusing.
  5. Clicking action, while good, requires a very stable surface in order to achieve a solid click/right-click action.
  6. Colleagues may want to use it as a coaster.

Recommendation: Want to/need to use Windows 8 on a touchless device? GET THIS! NOW!


02
Dec 12

Windows Store: Any Way to Figure out Who’s On First?

The recent statistics Microsoft handed out about regarding the Windows Store made me think a bit. Microsoft noted that some apps on the store have had significant numbers of downloads. The fact that several “parts of Windows 8 and Windows RT” are only available as a download from the Windows Store innately twists what “some apps have had millions of downloads from the Windows Store” can mean. Some third parties have claimed to have statistics on this as well. In general, only Microsoft can really know or reveal download statistics – I have no ability to see this information without Microsoft sharing it with me.

However, I can look at the data I do have and extrapolate from there…

I contend, however, that the submittal of feedback is a bit of very useful data. In particular, applications with significant numbers of ratings (“star”) submittals tend to reflect apps that have either incited positive or negative feedback from lots of users. So while lots of ratings submittals may not correlate exactly to the most downloaded apps, there is, I believe, a correlation indicating that lots of users have downloaded it, as only a percentage of users take the time to submit feedback (either the app was stellar and they say so, or it was crap and they don’t mince words). I’ve often noticed that there tends to be a vacuum of feedback in the middle of the feedback range (2-4 star), which I theorize is a bit of a “couch potato factor”. People are satiated enough with the app to not submit negative feedback, but not ecstatic enough to submit positive feedback.

Because I don’t poll every page for every app in every locale (I long ago changed this to try and be kind to Microsoft’s site), I can’t tell you the statistics across every locale – there could be some apps in some locales (in particular, I know there are in the China Windows Store) that have a very high count of ratings submittals as well). But I can tell you in the US Windows Store. So, what happens when I take a look at my entire list of apps, filtered down just to the US? Here’s the answer:

Out of the 30 apps with the most rating submittals, 19 are from Microsoft. Almost all of the Microsoft apps have also been on the store since August as well though – so the stats may be a bit confusing/misleading. What’s more interesting is that even with the barrage of Microsoft apps early on, prolific (promiscuous?) apps such as Skype, Netflix, Fruit Ninja, Cut The Rope, and Kindle have managed to eke their way into the list of apps with the most rating submittals. It’s also notable that an app from (what I believe is an) independent developer like Bernardo Zamora can both attract this volume of ratings submittals, and hold it’s review score as high as a 4.5! That isn’t easy to do.

So, while it isn’t possible for me to tell who the top downloaded Windows Store applications are, I think that this set of apps reflect a collection that lots of users are downloading.

Finally, while I probably shouldn’t really say anything here, it is notable that all of these apps in the top 30 support ARM. Um… Except two of them.

 


27
Nov 12

Windows Store: Developers, don’t stuff the store with clones!

Today while navigating the new Windows Store apps that arrived today, I ran across something that sort of broke my heart. I found dozens of copies of the same app from the same developer. Not identical, mind you. Subtle differences in how input boxes are laid out, as well as different names, colors, and application icons. Take a look at FlourMill here:

and then Personal Recipe Book here:

The developer, under the name LunaPlena, has submitted 118 apps in the last two weeks. Almost all but 3 of them (the three oldest) are effectively identical. They are the same “data input” application, with subtle design changes. It would be akin to Microsoft offering a version of Access for hair stylists, another for nail salons, etc. If you have a Windows 8 or Windows RT device, do a search for LunaPlena and you should see an innumerable number of Windows Store apps from the last week that are effectively identical.

This isn’t the only developer doing this, either – though the app is so similar, I have to wonder the relationship between the two. Developer Prafull Kelkar has 89 apps in the store. A few are actually an interesting “quiz-style” application like ADONetQuiz, but most of them are kindred spirits to MyProperties:

or GiftIsGot (which is of course ever so slightly different from GiftIsGave):

I guess in many ways, this isn’t that different from the cadre of developers I’ve seen submitting “quote” applications on the Windows Store (or the Apple App Store for that matter) where the engine of the app is identical, but one can choose a distinct app for each individual they want to find quotes for. Except here the engine is the same, and the candy shell for entering data changes. For what it’s worth, this also isn’t a problem unique to the Windows Store by any means. I’ve seen the same on the Apple store, and Microsoft even mentioned it in their Windows Phone Marketplace blog earlier this year, referring to it as “bulk publishing”, but not outright frowning on the process. I do distinctly recall Microsoft saying they frowned upon developers submitting multiple seemingly identical applications in the Windows Store, yet here we are, seeing exactly that.

Seeing developers do this is disappointing to me for a multitude of reasons. First, because it wastes time – Microsoft has to sort through a tedium of apps that will only ever be downloaded by a handful of users, when developers with a broader spectrum of consumer applicability get stuck in a queue behind them. Second, because it’s nonsensical. Customers with data entry needs would be better suited with one app that was more like Access, FileMaker (or even more likely, Bento), rather than almost 200 data entry apps that are subtly tweaked to each task. It shows a developer trying to flood the store, rather than one who truly crafts an application with broad appeal. Inundating the Windows Store with “fraternal twins” like this doesn’t help Windows 8/RT users find the applications that will make Windows 8/RT valuable to them, and it doesn’t help developers make money (heck – these are free apps we’re talking about here). Clusters of apps like this also make me feel even more that application counts – of anybody’s store are an emperor’s clothes comparison. Yet another reason why I have been de-emphasizing counts.


26
Nov 12

Why no news on winappupdate.com? I’ve been traveling!

Apologies for the lack of updates recently. While the Windows Store has been growing by ~500 apps per day worldwide, only a fraction of these are truly stellar apps, and filtering out the wheat is still a manual process – something I can only do when time allows. Similarly, my rollup reports of the store are a relatively manual process that I hope to automate someday. That day is not today. Given a subtle jab that might seem to infer a lack of news by me here is a lack of anything important in the Windows Store, I thought I’d clarify. I do try to check on on Twitter several times per day, but only do updates here when there is really major news or I’ve had time to do a major report.

This past month has been relatively insane for me, with Build, PASS Summit 2012, SharePoint Conference 2012, and vacation to the Internet-weak wilds of Wyoming for Thanksgiving with family last week. Real work has to come first for me, so that didn’t leave a lot of time for updates on the Windows Store. Combined with the lack of real huge news on the store (besides raw number growth, which I’m trying to move away from emphasizing, since it isn’t the most important metric by any means), there wasn’t much to post here, or time to post it. If you get lonely for updates here, please check Twitter!

I will be doing a rollup report this week, where I’ll discuss the state of the store, categories, which markets are strongest, and a few other details. Stay tuned.


14
Nov 12

Social is not the goal.

This week at the SharePoint Conference 2012, I attended a roundtable with two customers who have deployed Yammer within their organization and are pleased with the results. Last year I attended a roundtable with two customers who had deployed SharePoint 2010′s social features and were pleased with the results. The conversations were similar – and I can’t help but notice a pattern.

The pattern is the beating of the “social in the enterprise” drum. Not just by Microsoft either. Companies today will try to sell you social like others tried to sell you “mobile” in 2009, “cloud” in 2010,  or “apps” in 2011. It’s a buzzword that can mean something, but often means nothing. As a result, getting “social in the enterprise” when you buy many products is much like a teenager believing that if they get the latest fashions, that they’ll get friends in the in-crowd and a date with the person of their dreams. No, social isn’t an end. It isn’t really even a means to an end. It’s a shotgun that organizations keep grabbing for, hoping that they can fix what’s broken.

Read that again. Adopting “social” is really about fixing what’s broken. It really has nothing to do with “getting more social” at all. It has to do with repairing the organization, and its ability to communicate, collaboration, and archive and share knowledge.

Microsoft offers innumerable tools for collaboration. Let’s use that word “collaborate” broadly. Yammer, SharePoint, Exchange, Outlook, Windows 8/RT Mail, Windows Live Mail, Windows Live Messenger (soon to pass on to the great beyond), Skype, Lync, Office presence and co-authoring features, SkyDrive… Numerous names and numerous ways for, in many ways the same thing – tools that encourage users to work together and share better – or simply to share at all. Yet ironically each provides it’s own portal to information that users need to aggregate (or ignore).

Somehow along the way, we all got lost. The goal of all of these tools is the same – to connect entity A with a query with entity B (et al.) with knowledge or decision making capabilities.

I think in some ways an organization that is communicating effectively is somewhat like becoming enlightened – you never think about whether you are communicating effectively because you just are. It isn’t something you can build towards, it’s a state of being. Your organization is either communicating efficiently, or it isn’t.

As a result, we need to stop thinking about “putting more social options in front of users” like they’re food pellets for them to select from. I mentioned all of the tools that Microsoft produces above that are “social”. Alas, you add Twitter (one of my most useful knowledge-sharing/gleaning tools), Facebook, and any other external social network, and users aren’t lacking for social options. No, they are lacking tools to help them unify – to find the signal in the noise.

Subscribing to every single feed and every single document isn’t the answer either. We don’t necessarily need users to have more options to select from to build their knowledge. We need them to have better options. Better search that helps them find domain experts in a field they’re investigating, and help them broker knowledge sharing and find and learn from archived institutional knowledge that should be coveted. Better filtering that eliminates duplicity and reduces noise. We don’t want users getting back to the Pavlovian <DING> response so many of us got conditioned to with email alone. No, we need to learn how to integrate knowledge sharing into our daily lives, without letting it randomize us or break our ability to accomplish actual work. Fewer, better communication options, not a cornucopia.

Organizations today need to do more with less – and there is no indication that that will change anytime soon. As a result, we (all) need to start collaborating more efficiently – not just more. For years, organizations were able to simply look at a room full of minions and say, “Look. They’re diligently working.” When you have people chatting on Twitter, Facebook, or internal Exchange discussion aliases, it can often appear that they are not working – at least they are not working the way you are used to seeing them work on a computer – in diligent isolated silence – for the last 20 years.

This is the new world. It is time to kill the anti-social enterprise. We don’t have to do anything here, though. All we have to do is watch. Organizations need to enable their workers to find the communication tools that work for them, and help them to minimize waste and redundancy caused by individual knowledge silos. The social worker shouldn’t be stigmatized. The isolated worker should be emboldened to think beyond their own knowledge and skillset to learn from others. We are a storytelling species. Employees should be rewarded for sharing knowledge, for collaboration – for cross-team collaboration that may now have a clear marker in their annual review.

When I worked at Microsoft, Exchange discussion lists were the way we all shared knowledge. Much like Twitter, it would pass you by, but you could archive it to a PST, and some were archived to public folders. The information shared here was shared because it was important to someone. It was saved because it was important to someone else.  Important information resonates – it echoes. It reduces the need for every user in the organization to watch for the information, because it will cross their desk in a high visibility channel at some point. I worry with things like standardized email retention policies, this kind of institutional knowledge, and the value it represents, is being lost. Organizations that forget the past are condemned to repeat it.

In the end, we need social organizations – we need organic, collaborative organizations – because those that refuse to collaborate and grow, and encourage their employees to collaborate and build their individual knowledge and skillset – will die.

A standard joke has made the rounds for some time about the exec who asks another, “What if we teach our employees and give them valuable skills, and they leave?“, to which the other replies, “What if we don’t train them, and they stay?

CxOs around the world should be asking themselves the same thing about fostering cross-team information sharing, archival, and search throughout their organization. Social isn’t the goal, even if that is how a product or feature to fix it is sold to you. The goal is fixing broken, dysfunctional, or poorly functioning communication and information sharing in your organizations before it takes the whole ship down with it.


01
Nov 12

Windows RT, Sideloading, and Office. Oh my.

When you start working with Microsoft licensing – well, to be fair, almost anyone’s enterprise licensing, it can be mind-numbing. Truth be told, when I stepped up to pinch hit for my colleague, to cover the immense changes to SQL Server 2012 licensing, I developed a migraine with vertigo – something that hadn’t occurred for several years. While it could have been coincidence, we’ve taken liberty with it at work, and turned it into a running joke for our boot camps, that enterprise licensing can give you migraines.

In junior high school, we had a science experiment using perspective-flipping glasses (kind of like these). Now the lore goes, if you wear this kind of glasses day in and day out for 3-5 days, your mind will actually adjust, and flip the image right side up (take them off and it’ll take a while to reverse again). I could barely walk, and felt like I was going to hurl when I tried the glasses.

But licensing? I’ve been wearing those glasses for around six months, and you know what? My vision is stabilizing, and I can honestly almost walk straight. So while some people new to (Microsoft) licensing may look at certain things that Microsoft does and say, “WTH?”, I say, “It makes perfect sense – squint and turn your head upside down for a second”.

Two recent decisions from Microsoft fall in this same category:

  1. Office Home and Student in Windows RT not including commercial use rights.
  2. Windows RT requiring a… bit of work to enable sideloading of applications.

Now, these don’t necessarily have anything to do with each other, except they do. Follow along.

When you have a business model – whether it’s working or not, you like the line for revenue to go up (and operating expenses to ideally go down) – even if it’s just a little bit. Microsoft is fastidious about this. Keep earnings up, and don’t drop the income ball.

So why is H&S free for non-commercial users? Easy. Windows RT (and largely Windows 8) is all about consumers. Look no further than the marketing materials. Windows RT and Windows 8 are intended to bring Windows, touch, and power efficiency to a new world of devices (and ideally, stave off some/much of the appeal of the iPad by doing so). Some businesses may move to Windows 8 in short order, but most won’t. They’ll stick with Windows 7 until they see how, and where, they want to deploy Windows 8. In the meantime, the users within these businesses will buy iPads, Android tablets (somebody does, right?) and Windows RT tablets for home use, and wind up bringing them into the office. All three platforms bring legal landmines for Microsoft and other enterprise software. But this isn’t the place for me to dive into that. We offer a whole 2 day course that covers many of those issues. :-) So Windows RT includes Office as, really, a loss leader. It’s a prize at the bottom of the Windows RT box. I don’t mean to denegrate either product by saying that – but the goal is very clearly a better together strategy, even though Windows RT includes only a few of the Office apps, and limited  functionality when compared to Office on x86/x64.

By offering H&S as free on Windows RT, Microsoft can make that platform more appealing to consumers. By not including commercial use rights, Microsoft can ensure that (back to two paragraphs ago) it doesn’t harm their enterprise sales/Office 365 subscriptions/Software Assurance revenue as it does so. All of those are non-small numbers for Office.

Mary Jo Foley walked through how businesses can obtain commercial use rights, and in a nutshell, you buy Office 2013 for a user’s Windows 7/8 PC, they get commercial use rights for Windows RT (turning RT into a companion device by definition). Now, that means that for the business, Office on Windows RT isn’t free, but it also means it isn’t full price. In many ways, businesses get to take advantage of the multiple-device licenses that Office has had for some time (install on your primary and a secondary device), it’s just that the license is applied to Windows RT, rather than the actual bits as users would have historically done in the past. So that’s Office. What’s the deal with sideloading?

Matt’s lengthy walkthrough demonstrates the technical hurdles of sideloading apps (putting apps on Windows 8 or Windows RT without going through the Windows Store), but there’s a licensing angle here too – and in many ways it’s the same one I just demonstrated, if you put your glasses on and turn your head over.

Why is sideloading so complicated? Because there are three competing forces at play (in no particular order):

  1. Microsoft’s desire to keep the WinRT platform and Windows Store secure – sideloading gates what can/cannot run on these devices.
  2. Microsoft’s desire to keep the Windows Store as the preferred means of obtaining apps written for WinRT – retaining the 30% (or 20%) of revenue from app sales.
  3. Microsoft’s desire to (hum along if you know the tune) maintain Windows enterprise licensing sales – Enterprise includes sideloading. It’s a paid option on other editions.

By requiring a key for other versions, and requiring payment for that key, and requiring a minimum number of those licenses, Microsoft discourages “casual bypassing” or piracy of those keys as a mechanism to try and avoid using the Windows Store by tinkerers or hackers, or commercial distribution of apps that wouldn’t meet store guidelines, which is something sideloaded apps can do (see 1 and 2).

By not requiring any special keys or costs in Windows 8 Enterprise, Microsoft rewards those customers who have invested in SA (or Intune) and incentivizes customers on the fence about Windows client SA (or Intune) to take one of those avenues (see 3).

Like Active Directory membership was in the beginning (guilty!), sideloading is important, but I think may have been overblown in terms of either importance or complexity. The more I look at it, the more I realize that there are very few apps that will really require sideloading. Most commercial apps should be distributed on the Windows Store, either for sale (sharing revenue with Microsoft) or for free with a subscription (which, unlike Apple, for now at least, does not require revenue sharing with Microsoft). Instead, only enterprises building in-house Windows 8 and Windows RT line of business (LOB) apps will really need sideloading – at least as Microsoft would like it to exist.

As we start progressing to more of these enterprises building LOB apps, the need for sideloading may become more important. But I don’t anticipate most enterprises going into their own Windows 8 development lifecycle in short order (<6-12 months). They’re still trying to get their hands around the platform as a whole. That, combined with the lack of guidance on building LOB apps that align with the design principles Microsoft has been evangelizing for the last year, are taking, and will continue to take, some time for them to digest. Not that some companies won’t build their own WinRT LOB apps – some already are, and those may likely require sideloading. For customers with SA, which are likely to align reasonably well with those who have the time and energy to build apps for Windows 8 and Windows RT, the licensing “bumps” put in front of sideloading are likely a non-event. For consumers or hobbyists? Sideloading is a non-starter. Exactly as it was likely intended.

 


01
Nov 12

Windows Store: I’m holding out for a hero app

Last Thursday, my app counter went rather off the charts. Since the day before launch, the Windows Store has been adding 500 or so apps per day (with one exception). There aren’t a ton of stellar apps. I’m doing my best to document those that I do find on my Twitter feed, and I’m working on a better methodology. But for now, that’s where I put them.

On Thursday and Friday in particular, I expected a bump in the number of apps – and I saw that. One thing I saw struck me though. A lack of really distinct, platform exclusive apps.

Gaming consoles have historically had “hero titles” – exclusives that pull people to that platform because they can’t find them anywhere else. Those, theoretically, are the things that motivate consumers to buy consoles, and keep buying titles in that series from that publisher.

In the beginning, the iPhone had no hero titles. It had… no titles. Web apps or nothing. When the App Store arrived, it brought a gold rush of authors trying to make the most of the handheld, touch-driven, gyroscopic fundamentals of the iPhone platform (and make money). Among them? Angry Birds. Along the way, Rovio made themselves quite successful, as did a few other early iPhone developers, like Lima Sky (Doodle Jump) Pangea Software (Enigmo, etc). Many of the most successful games resulted in a virtuous cycle, as the titles were hero titles for the device, and the device was the exclusive place to get them. People bought iPhones (and then iPads) to play titles like Angry Birds, Enigmo, and eventually titles like (my personal favorite iPad game of all time), Contre Jour.

But in the end, exclusivity to a device matters little to independent developers – which is why you primarily see lock-in with hero titles that are primarily owned (Nintendo/Mario) or tightly licensed (and formerly owned – Microsoft/Halo). No, with independent developers, you see that they want to break free. To go promiscuously to almost any viable platform they think they can move to.

While Angry Birds did well on iOS, they moved to any other platform they could. I mean any platform. So today, when you tout that you have Angry Birds on your platform, it could be viewed as a staple (I hate the expression “table stakes”), but more likely it’s like saying your tires come with raised lettering. Nobody cares. What else can I do with your platform? I struggled with a name for these apps. A bunch of ideas were suggested when I asked on Twitter. But when I thought about it, the word that I realized I was thinking was promiscuous.

An app is promiscuous when it is as, or more concerned with it’s own viability than that of any platform it runs on. Examples of promiscuous apps? Angry Birds of course, but the Amazon Kindle Reader is probably the front-runner here. Though they make their own platform, the Kindle Reader has little shame, and will (luckily for content owners) run on almost any device. This compared to the iBooks app, which is so locked down, you can only read iBookstore content on handheld iOS devices. Other promiscuous apps? Netflix, Hulu, key video content providers, the NY Times, USA Today, etc. The amusing thing about almost all of these apps? They are literally about getting as many eyes as possible on content as possible.

To that end, a ton of the apps that have come into the Windows Store over the last week are just promiscuous apps. I’m not seeing stellar apps that are platform exclusives, and more importantly, I’m seeing a dearth of, well, productivity apps. I guess it’s only fair, right? Microsoft themselves said that writing productivity apps in WinRT is hard. Well, they didn’t say it was hard, they just didn’t bring Office over to the WinRT world. To be fair, it is going to be a ton of work to reproduce the productivity value of Office in a TDLFKAM world. A ton of work. I’ll write another post on this soon.

The other issue at this point is still a lack of some essential promiscuous apps. While Twitter surprised many (even seeming to surprise Ballmer during the Build keynote) by announcing they would create a distinct Twitter app for Windows 8. This is even more interesting given that Twitter recently killed Twitter for the Mac. Well, not technically killed – more created a zombie. While Twitter has promised a Windows Store app, Facebook and Microsoft are seemingly locked in a public “he said/she said” debate.

But I think the lack of apps that really help drive the plaform – hero games or hero applications, is a problem. We need to see more developers really taking chances with the Windows 8 platform, and finding things that you can do on Windows 8 and Windows RT that you can’t do easily on the iPad. (Do I know what these things are? No.)

It’s great to have the promiscuous titles, as it gives an air of familiarity to Windows RT and Windows 8 that users with earlier smartphones or tablets might expect to be there. But the hero titles are what pull people to the platform, and can help it grow and succeed – even if those hero titles shift to support other platforms in time too.

Update: A friend on Twitter pointed out, and he is correct, that Angry Birds wasn’t available until 2010, almost two years after the App Store debuted. So, my bad – it was a horrible example to use as a hero app – since it wasn’t even on iOS first, I believe it was on Facebook first. Apologies. Doodle Jump, Enigmo (and many of the Pangea titles, some of which were featured in the first Apple App Store commercials) are still good examples. Some comments below have pointed out that the platform will sell, which will bring app developers. This is definitely possible – it depends on how much the platform itself+the suite of “everywhere” apps, and the growing list of platform unique apps all appeal to them. The iPhone and iPad both benefited from a first-mover advantage, where the devices themselves motivated sellers before their app stores were even fully stocked. Trouble with a first-mover advantage is, it’s not usually available if you’re not the first mover, which, depending on how you look at Windows 8/Windows RT, Microsoft may or may not be the first mover. Regardless, there are a ton of dynamics at play here that really nobody can predict. It will be a fascinating holiday season to watch, and I look forward to seeing in the new year how Windows 8 and the Surface RT (and other Windows RT devices) have sold, and how well the Windows Store is stocked with titles that draw consumers. Again, apologies for the misstatement – and thanks for reading.