The New York Times is reporting that Microsoft CEO Steve Ballmer has recently been at a secret meeting with Adobe CEO Shantanu Narayen to discuss topics including the two companies' mutual competitor, Apple.

The Times says that the companies were investigating ways to partner in order to do battle with Apple. One option was for Microsoft to acquire Adobe, a claim that has seen Adobe's stock price surge by more than 10 percent.

Microsoft is thought to have investigated buying Adobe some years ago, but abandoned the idea with the expectation of running into new antitrust problems. With Apple and Google now such strong competitors, such a purchase may now be a viable option. Regardless of the legal difficulties, a partnership—and, indeed, a Microsoft purchase—makes sense.

The common enemy

Apple's increasing importance in the mobile space with its trio of iOS devices, the iPhone, iPod touch, and iPad, is a growing threat to both companies. Adobe and Apple butt heads in a number of markets. The two companies have competing software (Adobe's Lightroom and Premiere go up against Apple's Aperture and Final Cut Studio, for example), and more significantly, Apple is attacking a key Adobe product: Flash.

iOS devices have no Flash support in their browsers, so can't run Flash ads or any other Flash content on webpages. Apple has been advocating the use of HTML5, with its video and interactivity capabilities, as an alternative. Given the dominance of Flash in advertising, this is a big blow to Adobe. Apple then stepped up the pressure on Adobe with the launch earlier this year of iAds—rich, Flash-like ads built using HTML5.

Microsoft's difficulties in the mobile space—both phones and tablets—are well-known. The tablet problem is probably more serious; though Microsoft would like to have a piece of the smartphone market, it's tablets that threaten PC sales, and hence Windows. There is already some suggestion that iPad sales are denting netbook sales, and this is a trend that Microsoft could be badly hurt by. At the very least, it would substantially diminish home PC sales; ultimately, it could threaten corporate computer purchases too.

Apple's anti-Flash stance also indirectly threatens Microsoft. Redmond's relationship with HTML5 is a difficult one. On the one hand, the Internet Explorer team is making a considerable effort to make Internet Explorer 9 a modern browser with good support for new Web technology. That team, at least, is serious about HTML5.

On the other hand, Microsoft is also investing in its own Flash competitor, Silverlight, which it introduced in 2007 with great fanfare. Like Flash, Silverlight is a browser plugin that allows the creation of rich, interactive Web applications, and like Flash, it includes a range of media features not available to HTML5, such as DRM-protection of video streams. HTML5 threatens Silverlight in much the same way as it threatens Flash.

HTML5 also raises Microsoft's long-standing fear about the Web: that it would become a platform in its own right and displace the Windows PC. It is this fear that led to the development of Internet Explorer and the first browser war; Microsoft doesn't want the Web to be a platform, but if it must be one, it should be a Microsoft-powered Web accessed through a Microsoft browser on a Microsoft operating system.

Microsoft and Adobe do compete on a number of fronts. Silverlight and Flash, and ASP.NET and ColdFusion, are the two main areas of opposition. However, in practice, even in these competitive areas, the companies' respective products have carved out their own niches, and neither is threatening to completely demolish the other. Apple's stance towards Flash—get rid of it, use HTML5—is far more dangerous to Flash, and far more vigorously pursued, than Microsoft's stance—use this other browser plugin instead.

Collaboration and cooperation

Having a common enemy isn't enough to justify working together, of course. There needs to be some practical benefit to cooperation: something that strengthens both Microsoft and Adobe against the Apple threat.

The most obvious, immediate thing that the two companies can do is to get Flash ported to Windows Phone 7. Early signs are that Windows Phone 7's Web browser is surprisingly fast and capable, but one thing it isn't is HTML5-aware. If the phone operating system is successful, there will be a substantial growth in smartphones that are, at least for the time being, not HTML5-capable.

Such phones are crying out for Flash compatibility. There are certainly hurdles to achieving this—not least of which is the current requirement that all Windows Phone 7 software be written using .NET code—but they are by no means insurmountable. For example, Microsoft could simply bundle Flash with the phone operating system, and in so doing obviate the need for Flash to be written in C#.

The two companies could even go for something more exotic: make it possible to create Windows Phone 7 programs directly in Flash. The latest Flash version, CS 5, has the ability to produce iPhone applications. Apple originally planned to ban such applications, but has since relented. A similar capability could be readily built to produce Windows Phone 7 software.

Microsoft is already doing its best to court developers to attract them to its phone platform, with high-quality development tools that leverage the .NET technology that's already familiar to many. Flash development would similarly open the platform up to a large number of developers, letting them use technology they're already familiar and comfortable with.

There are technical things that the companies can work on, too, to improve the use of plugins in the desktop browsers. Google and Adobe are already cooperating to produce a better plugin interface to enable greater performance and stability for Flash in Chrome, and Chrome now bundles Flash. Taking a similar tack with Internet Explorer would further strengthen Flash's position on the desktop, again countering the forces of HTML5.