Tag Archives: microsoft

Media talking heads beginning to turn on Apple

Posted on by
1,896

You’re seeing an increasingly resentful attitude towards Apple on a lot of blogs and newspaper outlets these days:  Small but increasingly frequent editorial hints that Apple is no longer the darling underdog, but the resented 1000-pound gorilla that nobody can compete with.  I’ll give you a few examples:

On the day Apple became the #1 vendor of cell phones in the U.S. with 26%, All Things Digital put out the headline: “Android Surges… Apple Flat”.  Now when you’ve just eaten up a quarter of the market, it’s very hard to call you flat, but I’ll digress.  They are looking at OS shipments rather than product shipments.  From Apple’s point of view, the two are the same, and since Android isn’t a first-party OS, Apple gets the last laugh as the market leader. Still, it’s funny that the editor can call Apple “flat” on such a monumental day, especially when Android marketers are a half-dozen deep and Apple is just one company, with just one (or two) handset.   One thing ATD did get right is the fact that Blackberry is dying on the vine.

Another example is in the marching orders of the press corps towards treatment of the Android “family” of products (from a half-dozen different vendors) being treated as a single, monolithic anti-iphone. This depsite the fact that there are OEM features and major platform functionality differences on every handset.   Just compare an HTC to any phone with MotoBlur.  They really feel like entirely different products, but none in such a way that you can say yep this one is the “iPhone of Android devices”.

So I wonder if these journalistic tendencies are driven out of the desire to see Apple take a few bruisings now that they aren’t clawing at Microsoft from the bottom of the 32-bit barrel.

Bubble Sort: Could the Cloud be doomed by lazy programming?

Posted on by
2,045

Something occurred to me today while reading a Seattle Post Intelligencer article about how Pixar uses Microsoft’s Azure cloud computing solution for rendering its incredibly complex Renderman movie images: Could the availability of extreme computing resources like Azure lead to lazy, less-than-economical programming patterns?

Ie, would programmers be less likely to write highly productive code if less productive, less sophisticated code would yield the same result, given the availability of tons of hardware? And what would this mean in terms of energy conservation, and more importantly, the advancement of human thought?

Put another way, there are many ways to perform a certain computational algorithm, all yielding an accurate result, but all requiring various levels of computational intensity.  I’ll give an example.  First, the bubble sort.  This is a very simple, iterative method of sorting data into ordered lists–a method taught in basic computer programming classes. I first learned the bubble sort while taking Pascal at Cass Tech high school in Detroit.  I thought the bubble sort was awesome, although I later learned that there were other sorting schemes that were far faster and less computationally intense, ie. more economical.

So the hypothesis is this: innovation in more effective programming is lessened by the availability of horsepower.

How to save Windows Mobile

Posted on by
258

Among Blackberry, Microsoft, Google, and Apple, Microsoft was the earliest player in mobile computing and smart phones, so why have they failed in this area?

With Windows Mobile 7 waiting in the wings, it occurred to me that I just don’t see people using Windows Mobile devices that much any more. In fact, at work, we’ve seen a shift from WinMo to Blackberry and iPhone, with the exodus split about 60/40 in favor of Blackberry. The market share shift has been swift and decisive.

Now I know this isn’t exactly news, but I was trying to figure out why.  Microsoft correctly foresaw the mobile market as being the next big thing for them and the software industry, and they had very early foresight that mobile was going to sweep our eyes away from our desktops in a major way. They had the timing right, but their solution is, and has been, inadequate.

The Value of Ecosystems

One key difference between Microsoft and Apple is that, while they both offer end-to-end ecosystems (Microsoft with XBox, Apple with iTunes/iPhone/AppleTV), they seem to use their ecosystems to different ends.  I believe Apple’s tightly-integrated iTunes ecosystem was primarily driven by the “digital paranoia” of the record industry in the early 2000′s, and it may not have been Apple’s idea to provide such a closed environment. But, in the end, consumers seem to prefer the “just works” ecosystem over the “bring your own interface” approach. For this reason, Microsoft can be seen to have failed at establishing a clear content-to-consumer delivery model based on Windows Mobile.

What’s worse, the Zune, which could have been a great launchpad for a simplified, stylus-free version of Windows Mobile four years ago, exists on yet another Microsoft island, limiting its value to the consumer. Rectifying this problem by bringing the ill-fated Zune line into the limelight of the Windows ecosystem would go a long way towards making Windows Mobile relevant again. Think iPod.

Failure to Recognize Consumer Patterns of Behavior

It was only a matter of time before the average consumer was using personal devices to manage nearly every aspect of his life. Yet Microsoft took the wait and see approach, preferring to believe that the corporate world would drive personal device adoption, where, in reality, we can see that personal, entertainment-oriented device use has driven the entire mobile industry for the last several years.  Two parts gear lust, and one part nerdification of the general populous, this movement is the exact opposite of the strategy Microsoft used for Windows Mobile.

Most People Lose Their Stylus

The user interface options available on Windows Mobile devices, until recently, have been based on resistive touch screen technology, generally used with a small, inkless pen called a stylus.  Blackberry, by contrast, has always offered its trademark “scroll wheel”, and Apple developed a slew of UI technologies, including groundbreaking iPod controls, that culminated in a stylus-free touch-screen control environment for the iPhone. Windows Mobile never employed either approach, so solving this problem (and Microsoft is solving it) will help.

Give Developers a Reason to Develop

The real trick isn’t coming up with the idea. The real trick isn’t coding the program.  The real trick IS getting people to notice.  Apple has more than solved this problem, for better or worse, with the Appstore.  You bring the code, we bring the customers.  While some web sites have served as communities of developers and consumers of WinMo apps, they exist outside the ecosystem and don’t provide turnkey delivery of content.

When Microsoft finally did show up on the scene with an official WinMo store, they stubbed their toe by naming it “Windows Marketplace for Mobile”.  Srsly?

Stop Trying to Look Like Windows

Windows Mobile shouldn’t look like Windows and shouldn’t even be called “Windows”, since a windowing environment on a 3″ screen is a useless idea anyway. Yet when we look back at the releases of Windows Mobile (and its mobile predecessors), we get the idea that Microsoft has always wanted WinMo to look as much like desktop Windows as possible. Only with Windows Mobile 7 has this pattern been broken. (See above screen grab.)

Blackberry never had this problem, as their main objective was to develop a good mobile UI, and they had no ties to an existing desktop environment.  Apple, who does have Mac OS X, decided not to bother bringing the X look and feel to their mobile device. This was a great decision, of course.

Microsoft will rely on entrenchment as its primary market motivator

Posted on by
2,092

It’s clear to me now that Microsoft, one of the “great American companies” I often refer to when talking to my kids about things I admire in business, has switched from advancement to entrenchment as its retention strategy for existing customers.  That is, rather than move their platforms forward and pull global businesses along with them, a more defensive strategy is emerging–one where Microsoft tries not to hemorrhage too much business to Google and even Apple by reminding companies how cheap it is NOT to migrate away from the Microsoft eco-system.

A fantastic example of this dynamic came to light today when it was announced that the next version of Microsoft Office for Mac will replace Redmond’s clunky Entourage e-mail app with an actual Mac OS X version of Outlook, the predominant e-mail application used in medium and large enterprises.  My company alone supports somewhere in the neighborhood of twelve-hundred Outlook nodes at about fifteen different firms.  So a Mac version of Outlook, as the t-shirt saying goes, is “kind of a big deal.”

But what’s an even bigger deal is that Outlook once ran natively on the Mac–on Mac OS 9 anyway–and shared a great deal in common with its Windows cousin.  And, suffice it to say, it was a better product than its redheaded stepchild, Entourage.  It makes me wonder why they ever canned Outlook on the Mac to begin with.

Now I’m beginning to understand that Microsoft is on an all-hands mission to get as many enterprises, large and small, as entrenched as possible before Google and other market players really step to the plate with something that competes with Microsoft, and in particular Outlook and Office.  (Anybody who suggests that Google Apps currently beats Microsoft Office is smoking some pretty harsh crack, sorry guys.)

Entrenchment is the key to damage control: keep the customer believing that it will cost them more in dollars and difficulty to move away from Microsoft, no matter how compelling the alternative, and they’ll stick with Microsoft.  This was how they (soundly) destroyed Lotus Notes, and Redmond’s incredible staying power may allow it to stave off Google Apps for quite a few years to come.

Why does Microsoft still insist on using crummy brand names?

Posted on by
1,871

“Windows Marketplace for Mobile”.

OK, does this name strike anybody else as particularly dumb?  On the syllable count alone, the marketing folks at Microsoft should’ve shot this one down before it had a chance to get into the wild.  Now, it seems, it’s going to have to stick.

Compared to Apple’s “Appstore” (2 syllables) or Nokia’s “Ovi” (barely 2 syllables) or even Blackberry’s “App World” (seeing a pattern?), Microsoft’s elephant-sized name for it’s application store clocks in at a whopping 8 syllables. Imagine the water cooler discussions that will never happen as a result:

“Hey man, where’d you get that sweet pinball game?”

“Well, I got it from Windows Marketplace for Mobile!”

Riiiight.  Who seriously is going to call it that?  Microsoft’s history of self-defeating brand names hasn’t been on display this starkly since “Microsoft Windows Server Base Operating Systems Management Pack for Microsoft Operations Manager 2005“.  Srsly, who uses this wordy terminology?

With Apple having already coined the de facto term “Appstore”, why doesn’t Redmond take advantage of the growing strength of the Zune brand and call their wordy app store something like “Zune Store” or “Zune Place” or even just “Mobile World”?  Even HandMarket, a third-party app store for Windows Mobile, beats Microsoft to the punch in succinctness.

Apple: Decide if the iPhone is a platform, and do it quick please

Posted on by
133

If Apple insists on barring developers who overlap the “built-in functionality” of the iPhone, how is a developer to know what types of applications are a safe bet–in the long run? Since Apple recently banished Google Voice from the app store (which is an epic fail on Apple’s part, btw), one has to wonder, since all apps borrow some of Apple’s API functionality, just what they consider built-in and not.

The article, Apple Makes the Case for Web Apps concludes that developers will be more inclined to  create web-based apps geared at the iPhone.  While Apple’s recent actions may give developers pause to consider the web approach, I disagree that many will abandon their native app inclinations because of all that they lose in doing so.  For one, you can’t create home screen shortcuts to web apps (that I know of).  But the best reason not to develop web apps for the iPhone is their lack of support for front-end controls on the phone itself.  That is, in a web app, you don’t have nearly the power to access the GPS location, the GUI controls, the iPod library,  and so on. The new 3.0 iPhone browser is better at hooking into the phone’s local hardware, but is still quite hobbled compare to native apps, so geolocation and photos won’t have the pinache they would on a native app. Those are the content items that have made iPhone apps so much better than previous-generation mobile apps, and with the web approach, they’re more or less off limits.

How is it that YellowPages.com can offer a directory lookup app on the app store when it obviously overlaps Apple’s built-in Contacts and Maps functionality?  Yet instead of picking on YellowPages.com, Apple is seen picking on Google, arguably their biggest and most powerful ally.  Add to that the insult of Apple’s marketing of the iPhone and iPod Touch to developers as a platform for great apps, and it should make us all feel a bit used.

In the heady days of the computer revolution, Microsoft was forced to recognize that Windows (even MS-DOS) was a platform. Rather than stifling upstart competition by barring certain developers from the Windows ecosystem, Microsoft at least realized that it was developer embrace of the platform that would cause it to live or die in the long run.  The result was that, through the early 2000′s, Windows was the go-to platform for the whole world, and everybody from Sun to IBM lost lengthy, futile, billion dollar battles trying to undo Microsoft’s early decision.

Apple is nearly past that point in their new platform’s life cycle.  If it’s an app platform–let it be.  Palm and Blackberry are still waiting in the wings, and Windows Mobile will be the centerpiece of Microsoft’s revenue strategy in the next ten years.  And, like it or not, whatever else Microsoft did that was crummy and evil, they never told a developer he couldn’t distribute an app.

The Intrigue of an Appstore for Windows and OS X

Posted on by
2,469

Let’s face it.  If you can support selling 5 GB downloads (which Apple does in the form of movies) through your e-commerce solution, iTunes, then there’s certainly no intrinsic barrier to doing so with applications, or drivers, or other forms of digital content.  If we fail to think of applications as content, we fail in our understanding of content.   Yet here we are thinking it’s a bold new idea to license and sell application software online–fully confining the novelty of such a thing to the mobile space.   Heh, we’re smart.

An old friend, Fleecy Moss, who was among the architects of the independent takeover of Amiga in the early 2000′s, once gave a talk at a tradeshow in the nineties–and his espousal of the content designation to software was, at the time, a revolutionary concept.  As with many ideas that bubbled up from the ill-fated Amiga wellspring, this concept proved true, and was ahead of its time.  It would be another ten years before the idea was accepted by the greater community.

The app store paradigm has brought this idea to the forefront of the way we think about distributing content.  Yet there’s something holding up the adoption of online app stores to distribute software, and I can’t quite thumb it.  Shareware authors have been distributing license credentials through e-commerce sites for a decade already, yet Apple and Microsoft still don’t sell their developers’ software through their flagship web sites.

Perhaps even more silly is the fact that consumers, vis-a-vis bloggers, don’t already demand such a solution.  If I can buy and download a DRM’d episode of Lost, why can’t I download a credentialed, licensed copy of Squeeze, or Microsoft Office for Mac, or my favorite blogging application, Ecto?   Yet nobody complains.  Indeed, it seems that the idea of a desktop app store is some kind of new idea. Technologizer, the “smarter take on tech”, just ran a piece about it today.   Yet I was talking about it a year ago, and longer.

10 Truths Revealed by the MySpace/Microsoft Teamup

Posted on by
1,227

In honor of MyCrosoft.

1 – Microsoft lost big when it walked away empty-handed from Facebook, and Redmond’s been regretting it ever since.

2- Microsoft’s unexciting efforts in the music-business, including the Zune, may now have renewed hope, as MySpace is probably the only real 2.0 music destination on the web (iTunes is hardly a 2.0 destination; nice try Apple fans).

3 – Silverlight sucks and nobody wants it except Redmond.  Those page takeover ads for the next Batman movie that you see on MySpace occur courtesy of Flash, not Silverlight.  Of course, this won’t change that, either.

4 – MySpace is desperate to clean up its image as the red light district of social networking.  Who better than squeaky-clean Microsoft to bring a little much-needed legitimacy to the table?

5 – There are a greater percentage of Mac users on Facebook than on MySpace.  OK, I’m guessing here. But I bet there’s a pretty Mac-favorable ratio on the Facebook side that doesn’t exist on MySpace.

6 – Windows Mobile is late to the social networking party, and not fashionably so.  Hey, wait, what party ISN’T Windows Mobile late to?

7 – Microsoft would consider making an offer for MySpace, if it weren’t for the horrible fact that MySpace is the world’s largest ColdFusion abuser.  Eek, that’ll scare off a .Net dev in a hurry.

8 – MySpace’s Hold ‘Em poker apps are better than Facebook’s.  (It’s true.)

9 – Microsoft holds in very high regard the design ethic of MySpace (which looks like a 1998-era web site and always causes people to wonder where in the hell the link to edit a photo album is).

10 – MySpace still garners some undeniable clout, even if it’s with a segment of consumers that are less likely to have graduated college and more likely to still be rocking a Pentium 3.