In my view, the Second Circuit’s decision in Apple e-Books, if not reversed by the Supreme Court, threatens to undo a half century of progress in reforming antitrust doctrine. In decision after decision, from White Motors through Leegin and Actavis, the Supreme Court has repeatedly held—in cases involving both horizontal and vertical restraints—that the only test for whether an agreement can be found per se unlawful under Section 1 is whether it is “a naked [restraint] of trade with no purpose except stifling competition,” or whether it is instead “ancillary to the legitimate and competitive purposes” of a business association. Dagher. The cases in which the Court has consistently applied this test read like a litany of antitrust decisions we all now study in law school: White Motors, Topco, GTE Sylvania, Professional Engineers, BMI, Maricopa, NCAA, Business Electronics, ARCO, California Dental, Dagher, Leegin, American Needle, and, most recently, Actavis. Significantly, more than two-thirds of these cases involved horizontal, not vertical restraints.

Read the full piece here.

As ICLE argued in its amicus brief, the Second Circuit’s ruling in United States v. Apple Inc. is in direct conflict with the Supreme Court’s 2007 Leegin decision, and creates a circuit split with the Third Circuit based on that court’s Toledo Mack ruling. Moreover, the negative consequences of the court’s ruling will be particularly acute for modern, high-technology sectors of the economy, where entrepreneurs planning to deploy new business models will now face exactly the sort of artificial deterrents that the Court condemned in Trinko…

Read the full piece here.

On balance the Second Circuit was right to apply the antitrust laws to Apple.

Right now the Supreme Court has before it a petition for Certiorari, brought by Apple, Inc., which asks the Court to reverse the decision of the Second Circuit. That decision found per se illegality under the Sherman Act, for Apple’s efforts to promote cooperation among a group of six major publishers, who desperately sought to break Amazon’s dominant position in the ebook market. At that time, Amazon employed a wholesale model for ebooks under which it bought them for a fixed price, but could sell them for whatever price it wanted, including sales at below cost of popular books treated as loss leaders. These sales particularly frustrated publishers because of the extra pressure they placed on the sale of hard cover and paper back books. That problem disappeared under the agency relationship model that Apple pioneered. Now the publishers would set the prices for the sale of their own volumes, and then pay Apple a fixed commission for its services in selling the ebooks.

Read the full piece here.

For a few months I have thought that the Apple eBooks case would find an easy fit within the Supreme Court’s antitrust decisions. The case that seems closest to me is Business Electronics v. Sharp Electronics, an unfortunately under-appreciated piece of antitrust precedent. One sign of its under-appreciation is its absence in some recent editions of antitrust casebooks.

Read the full piece here.

The appellate court’s 2015 decision affirming the district court’s finding of per se liability in United States v. Apple provoked controversy over the legal and economic merits of the case, its significance for antitrust jurisprudence, and its implications for entrepreneurs, startups, and other economic actors throughout the economy. Apple has filed a cert petition with the Supreme Court, which will decide on February 19th whether to hear the case.

Read the full piece here.

The Ninth Circuit made waves recently with its decision in Lenz v. Universal Music Corp., in which it decided that a plaintiff in a copyright infringement case must first take potential fair use considerations into account before filing a takedown notice under the DMCA. Lenz, represented by the EFF, claimed that Universal had not formed a good faith belief that an infringement had occurred as required by § 512(c)(3)(A)(v). Consequently, Lenz sought damages under § 512(f), alleging that Universal made material misrepresentations in issuing a takedown notice without first considering a fair use defense.

In reaching its holding, the Ninth Circuit decided that fair use should not be considered an affirmative defense–which is to say that it is not properly considered after an allegation, but must be considered when determining whether a prima facie claim exists. It starts from the text of the Copyright Act itself. According to 17 U.S.C. § 107

Notwithstanding the provisions of sections 106 and 106A, the fair use of a copyrighted work … is not an infringement of copyright.

In support of its contention, the Ninth Circuit goes on to cite a case in the Eleventh Circuit as well as legislative material suggesting that Congress intended that fair use no longer be considered as an affirmative defense. Thus, in the Ninth Circuit’s view, such fair use at best qualifies as a sort of quasi-defense, and most likely constitutes an element of an infringement claim. After all, if fair use is literally non-infringing, then establishing infringement requires ruling out fair use, as well.

Or so says the Ninth Circuit. But it takes little more than a Google search — let alone the legal research one should expect of federal judges and their clerks — to realize that the court is woefully, and utterly, incorrect.

Is Fair Use an Affirmative Defense ?

The Supreme Court has been perfectly clear that fair use is in fact an affirmative defense. In Campbell v. Acuff-Rose, the Supreme Court had occasion to consider the nature of fair use under § 107 in the context of determining whether 2 Live Crew’s parody of Roy Orbison’s “Pretty Woman” was a permissible use. In considering the fourth fair use factor, “the effect of the use upon the potential market for or value of the copyrighted work,” the Court held that “[s]ince fair use is an affirmative defense, its proponent would have difficulty carrying the burden of demonstrating fair use without favorable evidence about relevant markets.”

Further, in reaching this opinion the Court relied on its earlier precedent in Harper & Row, where, in discussing the “purpose of the use” prong of § 107, the Court said that “[t]he drafters [of § 107] resisted pressures from special interest groups to create presumptive categories of fair use, but structured the provision as an affirmative defense requiring a case-by-case analysis.”  Not surprisingly, other courts are inclined to follow the the Supreme Court. Thus the Eleventh Circuit, the Southern District of New York, and the Central District of California (here and here), to name but a few, all explicitly refer to fair use as an affirmative defense. Oh, and the Ninth Circuit did too, at least until Lenz.

The Ninth Circuit Dissembles

As part of its appeal, Universal relied on the settled notion that fair use is an affirmative defense in building its case. Perhaps because this understanding of fair use is so well established, Universal failed to cite extensively why this was so. And so (apparently unable to perform its own legal research), the Ninth Circuit dismissed § 107 as an affirmative defense out of hand, claiming that

Universal’s sole textual argument is that fair use is not “authorized by the law” because it is an affirmative defense that excuses otherwise infringing conduct … Supreme Court precedent squarely supports the conclusion that fair use does not fall into the latter camp: “[A]nyone who . . . makes a fair use of the work is not an infringer of the copyright with respect to such use.” Sony Corp. of Am. v. Universal City Studios, Inc., 464 U.S. 417, 433 (1984).”

It bears noting that the Court in Sony Corp. did not discuss whether or not fair use is an affirmative defense, whereas Acuff Rose (decided 10 years after Sony Corp.) and Harper & Row decisions do.

To shore up its argument, the Ninth Circuit then goes on to cite the Eleventh Circuit for the notion that the 1976 Act fundamentally changed the nature of fair use, moving it away from its affirmative defense roots. Quoting Bateman v. Mnemonics, Inc., the court claims that

Although the traditional approach is to view “fair use” as an affirmative defense, . . . it is better viewed as a right granted by the Copyright Act of 1976. Originally, as a judicial doctrine without any statutory basis, fair use was an infringement that was excused—this is presumably why it was treated as a defense. As a statutory doctrine, however, fair use is not an infringement. Thus, since the passage of the 1976 Act, fair use should no longer be considered an infringement to be excused; instead, it is logical to view fair use as a right. Regardless of how fair use is viewed, it is clear that the burden of proving fair use is always on the putative infringer.

But wait — didn’t I list the Eleventh Circuit as one of the (many) courts that have held fair use to be an affirmative defense? Why yes I did. It turns out that, as Devlin Hartline pointed out last week, the Ninth Circuit actually ripped the Eleventh Circuit text completely out of context. The full Bateman quote (from a footnote, it should be noted) is as follows:

Fair use traditionally has been treated as an affirmative defense to a charge of copyright infringement …. In viewing fair use as an excused infringement, the court must, in addressing this mixed question of law and fact, determine whether the use made of the original components of a copyrighted work is “fair” under 17 U.S.C. § 107 … Although the traditional approach is to view “fair use” as an affirmative defense, this writer, speaking only for himself, is of the opinion that it is better viewed as a right granted by the Copyright Act of 1976. Originally, as a judicial doctrine without any statutory basis, fair use was an infringement that was excused—this is presumably why it was treated as a defense. As a statutory doctrine, however, fair use is not an infringement. Thus, since the passage of the 1976 Act, fair use should no longer be considered an infringement to be excused; instead, it is logical to view fair use as a right. Regardless of how fair use is viewed, it is clear that the burden of proving fair use is always on the putative infringer.” (internal citations omitted, but emphasis added)

Better yet, in a subsequent opinion the Eleventh Circuit further clarified the position that the view of fair use as an affirmative defense is binding Supreme Court precedent, notwithstanding any judge’s personal preferences to the contrary.

But that’s not the worst of it. Not only did the court shamelessly misquote the Eleventh Circuit in stretching to find a justification for its prefered position, the court actually ignored its own precedent to the contrary. In Dr. Seuss Enterprises, L.P. v. Penguin Books USA, Inc., the Ninth Circuit held that

Since fair use is an affirmative defense, [the Defendant-Appellants] must bring forward favorable evidence about relevant markets. Given their failure to submit evidence on this point … we conclude that “it is impossible to deal with [fair use] except by recognizing that a silent record on an important factor bearing on fair use disentitle[s] the proponent of the defense[.]

Further, even if the Lenz court is correct that § 107 “unambiguously contemplates fair use as a use authorized by the law” — despite Supreme Court precedent — the authority the Ninth Circuit attempts to rely upon would still require defendants to raise a fair use defense after a prima facie claim was made, as “the burden of proving fair use is always on the putative infringer.”  

It Also Violates a Common Sense Reading of the DMCA

As with all other affirmative defenses, a plaintiff must first make out a prima facie case before the defense can be raised. So how do we make sense of the language in § 107 that determines fair use to not be infringement? In essence, it appears to be a case of inartful drafting.  Particularly in light of the stated aims of the DMCA — a law that was enacted after the Supreme Court established that fair use was an affirmative defense — the nature of fair use as an affirmative defense that can only be properly raised by an accused infringer is as close to black letter law as it gets.

The DMCA was enacted to strike a balance between the interests of rightsholders in protecting their property, and the interests of society in having an efficient mechanism for distributing content. Currently, rightsholders send out tens of millions of takedown notices every year to deal with the flood of piracy and other infringing uses. If rightsholders were required to consider fair use in advance of each of these, the system would be utterly unworkable — for instance, in Google’s search engine alone, over 54 million removal requests were made in just the month of August 2015 owing to potential copyright violations. While the evisceration of the DMCA is, of course, exactly what the plaintiffs (or more accurately, EFF, which represented the plaintiffs) in Lenz wanted, it’s not remotely what the hard-wrought compromise of the statute contemplates.

And the reason it would be unworkable is not just because of the volume of the complaints, but because fair use is such an amorphous concept that ultimately requires adjudication.

Not only are there four factors to consider in a fair use analysis, but there are no bright line rules to guide the application of the factors. The open ended nature of the defense essentially leaves it up to a defendant to explain just why his situation should not constitute infringement. Until a judge or a jury says otherwise, how is one to know whether a particular course of conduct qualifies for a fair use defense?

The Lenz court even acknowledges as much when it says

If, however, a copyright holder forms a subjective good faith belief the allegedly infringing material does not constitute fair use, we are in no position to dispute the copyright holder’s belief even if we would have reached the opposite conclusion. (emphasis added)

Thus, it is the slightest of fig leaves that is necessary to satisfy the Lenz court’s new requirement that fair use be considered before issuing a takedown notice.

What’s more, this statement from the court also demonstrates the near worthlessness of reading a prima facie fair use requirement into the takedown requirements. Short of a litigant explicitly disclaiming any efforts to consider fair use, the standard could be met with a bare assertion. It does, of course, remain an open question whether the computer algorithms the rightsholders employ in scanning for infringing content are actually capable of making fair use determinations — but perhaps throwing a monkey wrench — any monkey wrench — into the rightsholders’ automated notice-and-takedown systems was all the court was really after. I think we can at least be sure that that was EFF’s aim, anyway, as they apparently think that § 512 tends to be a tool of censorship in the hands of rightsholders.

The structure of the takedown and put-back provisions of the DMCA also cut against the Lenz court’s view. The put-back requirements of Section 512(g) suggest that affirmative defenses and other justifications for accused infringement would be brought up after a takedown notice was submitted. What would be the purpose of put-back response, if not to offer the accused infringers justifications and defenses to an allegation of infringement? Along with excuses such as having a license, or a work’s copyright being expired, an alleged infringer can bring up the fair use grounds under which he believed he was entitled to use the work in question.

In short, to require a rightsholder to analyze fair use in advance of a takedown request effectively requires her to read the mind of an infringer and figure out what excuse that party plans to raise as part of her defense. This surely can’t have been what Congress intended with the takedown provisions of the DMCA — enacted as they were years after the Supreme Court had created the widely recognized rule that fair use is an affirmative defense.

Well, widely recognized, that is, except in the Ninth Circuit. This month, anyway.

Update: I received some feedback on this piece which pointed out an assumption I was making with respect to the Ninth Circuit’s opinion, and which deserves a clarifying note. Essentially, the Lenz court splits the concept of affirmative defenses into two categories: (1) an affirmative defense that is merely a label owing to the procedural posture of a case and (2) an affirmative defense, as it is traditionally understood and that always puts the burden of production on a defendant.  By characterizing affirmative defenses in this way, the Lenz court gets to have its cake and eat it too:  when an actual proceeding is filed, a defendant will procedurally have the burden of production on the issue, but since fair use is at most a quasi-affirmative defense, the court felt it was fair to shift that same burden onto rightsholders when issuing a takedown letter.  So technically the court says that fair use is an affirmative defense (as a labeling matter), but it does not practically treat is as such for the purposes of takedown notices.

Filed under: copyright, intellectual property Tagged: copyright, Intellectual property

On Thursday I will be participating in an ABA panel discussion on the Apple e-books case, along with Mark Ryan (former DOJ attorney) and Fiona Scott-Morton (former DOJ economist), both of whom were key members of the DOJ team that brought the case. Details are below. Judging from the prep call, it should be a spirited discussion!

Readers looking for background on the case (as well as my own views — decidedly in opposition to those of the DOJ) can find my previous commentary on the case and some of the issues involved here:

• Why I think the Apple e-books antitrust decision will (or at least should) be overturned
• Why I think the government will have a tough time winning the Apple e-books antitrust case
• The procompetitive story that could undermine the DOJ’s e-books antitrust case against Apple
• How Apple can defeat the DOJ’s e-book antitrust suit
• The US e-books case against Apple: The procompetitive story (in a special issue of Concurrences on “E-books and the boundaries of antitrust” that includes several other essays worth reading)
• Amazon vs. Macmillan: It’s all about control

Other TOTM authors have also weighed in. See, e.g.:

• Alden Abbott: The Second Circuit Misapplies the Per Se Rule in U.S. v. Apple
• Josh Wright: The Apple E-Book Kerfuffle Meets Alfred Marshall’s Principles of Economics
• Josh Wright: Apple and Amazon E-Book Most Favored Nation Clauses

DETAILS:

ABA Section of Antitrust Law

Federal Civil Enforcement Committee, Joint Conduct, Unilateral Conduct, and Media & Tech Committees Present:

“The 2d Cir.’s Apple E-Books decision: Debating the merits and the meaning”

July 16, 2015
12:00 noon to 1:30 pm Eastern / 9:00 am to 10:30 am Pacific

On June 30, the Second Circuit affirmed DOJ’s trial victory over Apple in the Ebooks Case. The three-judge panel fractured in an interesting way: two judges affirmed the finding that Apple’s role in a “hub and spokes” conspiracy was unlawful per se; one judge also would have found a rule-of-reason violation; and the dissent — stating Apple had a “vertical” position and was challenging the leading seller’s “monopoly” — would have found no liability at all. What is the reasoning and precedent of the decision? Is “marketplace vigilantism” (the concurring judge’s phrase) ever justified? Our panel — which includes the former DOJ head of litigation involved in the case — will debate the issues.

Moderator

• Ken Ewing, Steptoe & Johnson LLP

Panelists

• Geoff Manne, International Center for Law & Economics
• Fiona Scott Morton, Yale School of Management
• Mark Ryan, Mayer Brown LLP

Register HERE

Filed under: administrative, antitrust, cartels, contracts, doj, e-books, economics, Efficiencies, error costs, law and economics, litigation, market definition, MFNs, monopolization, resale price maintenance, technology, vertical restraints Tagged: agency model, Amazon, antitrust, Apple, doj, e-books, iBookstore, major publishers, MFN, most favored nations clause, per se, price-fixing, publishing industry, Rule of reason, vertical restraints

Last year, Microsoft’s new CEO, Satya Nadella, seemed to break with the company’s longstanding “complain instead of compete” strategy to acknowledge that:

We’re going to innovate with a challenger mindset…. We’re not coming at this as some incumbent.

Among the first items on his agenda? Treating competing platforms like opportunities for innovation and expansion rather than obstacles to be torn down by any means possible:

We are absolutely committed to making our applications run what most people describe as cross platform…. There is no holding back of anything.

Earlier this week, at its Build Developer Conference, Microsoft announced its most significant initiative yet to bring about this reality: code built into its Windows 10 OS that will enable Android and iOS developers to port apps into the Windows ecosystem more easily.

To make this possible… Windows phones “will include an Android subsystem” meant to play nice with the Java and C++ code developers have already crafted to run on a rival’s operating system…. iOS developers can compile their Objective C code right from Microsoft’s Visual Studio, and turn it into a full-fledged Windows 10 app.

Microsoft also announced that its new browser, rebranded as “Edge,” will run Chrome and Firefox extensions, and that its Office suite would enable a range of third-party services to integrate with Office on Windows, iOS, Android and Mac.

Consumers, developers and Microsoft itself should all benefit from the increased competition that these moves are certain to facilitate.

Most obviously, more consumers may be willing to switch to phones and tablets with the Windows 10 operating system if they can continue to enjoy the apps and extensions they’ve come to rely on when using Google and Apple products. As one commenter said of the move:

I left Windows phone due to the lack of apps. I love the OS though, so if this means all my favorite apps will be on the platform I’ll jump back onto the WP bandwagon in a heartbeat.

And developers should invest more in development when they can expect additional revenue from yet another platform running their apps and extensions, with minimal additional development required.

It’s win-win-win. Except perhaps for Microsoft’s lingering regulatory strategy to hobble Google.

That strategy is built primarily on antitrust claims, most recently rooted in arguments that consumers, developers and competitors alike are harmed by Google’s conduct around Android which, it is alleged, makes it difficult for OS makers (like Cyanogen) and app developers (like Microsoft Bing) to compete.

But Microsoft’s interoperability announcements (along with a host of other rapidly evolving market characteristics) actually serve to undermine the antitrust arguments that Microsoft, through groups like FairSearch and ICOMP, has largely been responsible for pushing in the EU against Google/Android.

The reality is that, with innovations like the one Microsoft announced this week, Microsoft, Google and Apple (and Samsung, Nokia, Tizen, Cyanogen…) are competing more vigorously on several fronts. Such competition is evidence of a vibrant marketplace that is simply not in need of antitrust intervention.

The supreme irony in this is that such a move represents a (further) nail in the coffin of the supposed “applications barrier to entry” that was central to the US DOJ’s antitrust suit against Microsoft and that factors into the contemporary Android antitrust arguments against Google.

Frankly, the argument was never very convincing. Absent unjustified and anticompetitive efforts to prop up such a barrier, the “applications barrier to entry” is just a synonym for “big.” Admittedly, the DC Court of Appeals in Microsoft was careful — far more careful than the district court — to locate specific, narrow conduct beyond the mere existence of the alleged barrier that it believed amounted to anticompetitive monopoly maintenance. But central to the imposition of liability was the finding that some of Microsoft’s conduct deterred application developers from effectively accessing other platforms, without procompetitive justification.

With the implementation of initiatives like the one Microsoft has now undertaken in Windows 10, however, it appears that such concerns regarding Google and mobile app developers are unsupportable.

Of greatest significance to the current Android-related accusations against Google, the appeals court in Microsoft also reversed the district court’s finding of liability based on tying, noting in particular that:

If OS vendors without market power also sell their software bundled with a browser, the natural inference is that sale of the items as a bundle serves consumer demand and that unbundled sale would not.

Of course this is exactly what Microsoft Windows Phone (which decidedly does not have market power) does, suggesting that the bundling of mobile OS’s with proprietary apps is procompetitive.

Similarly, in reviewing the eventual consent decree in Microsoft, the appeals court upheld the conditions that allowed the integration of OS and browser code, and rejected the plaintiff’s assertion that a prohibition on such technological commingling was required by law.

The appeals court praised the district court’s recognition that an appropriate remedy “must place paramount significance upon addressing the exclusionary effect of the commingling, rather than the mere conduct which gives rise to the effect,” as well as the district court’s acknowledgement that “it is not a proper task for the Court to undertake to redesign products.”  Said the appeals court, “addressing the applications barrier to entry in a manner likely to harm consumers is not self-evidently an appropriate way to remedy an antitrust violation.”

Today, claims that the integration of Google Mobile Services (GMS) into Google’s version of the Android OS is anticompetitive are misplaced for the same reason:

But making Android competitive with its tightly controlled competitors [e.g., Apple iOS and Windows Phone] requires special efforts from Google to maintain a uniform and consistent experience for users. Google has tried to achieve this uniformity by increasingly disentangling its apps from the operating system (the opposite of tying) and giving OEMs the option (but not the requirement) of licensing GMS — a “suite” of technically integrated Google applications (integrated with each other, not the OS).  Devices with these proprietary apps thus ensure that both consumers and developers know what they’re getting.

In fact, some commenters have even suggested that, by effectively making the OS more “open,” Microsoft’s new Windows 10 initiative might undermine the Windows experience in exactly this fashion:

As a Windows Phone developer, I think this could easily turn into a horrible idea…. [I]t might break the whole Windows user experience Microsoft has been building in the past few years. Modern UI design is a different approach from both Android and iOS. We risk having a very unhomogenic [sic] store with lots of apps using different design patterns, and Modern UI is in my opinion, one of the strongest points of Windows Phone.

But just because Microsoft may be willing to take this risk doesn’t mean that any sensible conception of competition law and economics should require Google (or anyone else) to do so, as well.

Most significantly, Microsoft’s recent announcement is further evidence that both technological and contractual innovations can (potentially — the initiative is too new to know its effect) transform competition, undermine static market definitions and weaken theories of anticompetitive harm.

When apps and their functionality are routinely built into some OS’s or set as defaults; when mobile apps are also available for the desktop and are seamlessly integrated to permit identical functions to be performed on multiple platforms; and when new form factors like Apple MacBook Air and Microsoft Surface blur the lines between mobile and desktop, traditional, static anticompetitive theories are out the window (no pun intended).

Of course, it’s always been possible for new entrants to overcome network effects and scale impediments by a range of means. Microsoft itself has in the past offered to pay app developers to write for its mobile platform. Similarly, it offers inducements to attract users to its Bing search engine and it has devised several creative mechanisms to overcome its claimed scale inferiority in search.

A further irony (and market complication) is that now some of these apps — the ones with network effects of their own — threaten in turn to challenge the reigning mobile operating systems, exactly as Netscape was purported to threaten Microsoft’s OS (and lead to its anticompetitive conduct) back in the day. Facebook, for example, now offers not only its core social media function, but also search, messaging, video calls, mobile payments, photo editing and sharing, and other functionality that compete with many of the core functions built into mobile OS’s.

But the desire by apps like Facebook to expand their networks by being on multiple platforms, and the desire by these platforms to offer popular apps in order to attract users, ensure that Facebook is ubiquitous, even without any antitrust intervention. As Timothy Bresnahan, Joe Orsini and Pai-Ling Yin demonstrate:

(1) The distribution of app attractiveness to consumers is skewed, with a small minority of apps drawing the vast majority of consumer demand. (2) Apps which are highly demanded on one platform tend also to be highly demanded on the other platform. (3) These highly demanded apps have a strong tendency to multihome, writing for both platforms. As a result, the presence or absence of apps offers little reason for consumers to choose a platform. A consumer can choose either platform and have access to the most attractive apps.

Of course, even before Microsoft’s announcement, cross-platform app development was common, and third-party platforms like Xamarin facilitated cross-platform development. As Daniel O’Connor noted last year:

Even if one ecosystem has a majority of the market share, software developers will release versions for different operating systems if it is cheap/easy enough to do so…. As [Torsten] Körber documents [here], building mobile applications is much easier and cheaper than building PC software. Therefore, it is more common for programmers to write programs for multiple OSes…. 73 percent of apps developers design apps for at least two different mobiles OSes, while 62 percent support 3 or more.

Whether Microsoft’s interoperability efforts prove to be “perfect” or not (and some commenters are skeptical), they seem destined to at least further decrease the cost of cross-platform development, thus reducing any “application barrier to entry” that might impede Microsoft’s ability to compete with its much larger rivals.

Moreover, one of the most interesting things about the announcement is that it will enable Android and iOS apps to run not only on Windows phones, but also on Windows computers. Some 1.3 billion PCs run Windows. Forget Windows’ tiny share of mobile phone OS’s; that massive potential PC market (of which Microsoft still has 91 percent) presents an enormous ready-made market for mobile app developers that won’t be ignored.

It also points up the increasing absurdity of compartmentalizing these markets for antitrust purposes. As the relevant distinctions between mobile and desktop markets break down, the idea of Google (or any other company) “leveraging its dominance” in one market to monopolize a “neighboring” or “related” market is increasingly unsustainable. As I wrote earlier this week:

Mobile and social media have transformed search, too…. This revolution has migrated to the computer, which has itself become “app-ified.” Now there are desktop apps and browser extensions that take users directly to Google competitors such as Kayak, eBay and Amazon, or that pull and present information from these sites.

In the end, intentionally or not, Microsoft is (again) undermining its own case. And it is doing so by innovating and competing — those Schumpeterian concepts that were always destined to undermine antitrust cases in the high-tech sector.

If we’re lucky, Microsoft’s new initiatives are the leading edge of a sea change for Microsoft — a different and welcome mindset built on competing in the marketplace rather than at regulators’ doors.

Filed under: antitrust, barriers to entry, exclusionary conduct, google, market definition, markets, monopolization, technology, tying, tying Tagged: Android, antitrust, competition, Cyanogen, google, Google Mobile Services, innovation, microsoft, Mobile, Satya Nadella, tying, Windows Phone