Two New Antitrust Bills Could Increase App Store Competition and Spark Discussion of Privacy and Security as Consumer Welfare Metrics

By: Zoe Wood

In the first quarter of 2022, Apple beat its own record for quarterly spending on lobbying ($2.5 million). What’s the occasion? Two new antitrust bills which threaten Apple’s dominance over its App Store are gaining ground in Congress.

What Bills? 

In late January, the Senate Judiciary Committee voted to advance the American Innovation and Choice Online Act by a vote of 16 to 6. Just a few weeks later, the Committee advanced the Open App Markets Act by a vote of 20 to 2. 

The bills are similar, however, the former has more sweeping coverage. It applies to all “online platforms” with 50,000,000 or more monthly active US-based individual users or 100,000 monthly active US-based business users which (1) enable content generation and content viewing and interaction (i.e., Instagram, Twitter, Spotify, etc.), (2) facilitate online advertising or sales of products or services of any sort (i.e., Amazon, etc.), or (3) enable searches that “access or display a large volume of information” (i.e., Google, etc.). The bill describes ten categories of prohibited conduct, all aimed at curbing covered platforms’ preferential treatment of their own products or services over other products on the platform. 

For example, the Act would prohibit “covered platforms” from “limit[ing] the ability of the products, services, or lines of business of another business user to compete on the covered platform relative to the products, services, or lines of business of the covered platform operator in a manner that would materially harm competition.” 

The latter act, the Open App Markets Act, in contrast would apply to “any person that owns or controls an app store” with over 50,000,000 US-based users. It proceeds by identifying and defining app store behaviors which are purportedly anticompetitive. For example, the Act would prohibit an app store from conditioning distribution of an app on its use of store-controlled payment systems as the in-app payment system. The Act would also prohibit app stores from requiring developers to offer apps on pricing terms equal to or more favorable than those on other app stores and from punishing a developer for doing so. Similar to the Innovation and Choice Online Act, the Open App Markets Act prohibits covered app stores from preferential treatment towards their own products in the app store search function.

Why Does Apple Oppose These Bills (Aside from the Obvious)? 

While the obvious answer (the bills would diminish Apple’s dominance and therefore diminish its profit) is probably also correct, Apple has put forward a different reason for its opposition to the acts. In a January 18th letter addressed to Senators Durbin, Grassley, Klobuchar, and Lee, and signed by Apple’s Senior Director of Government Affairs Timothy Powderly, Apple expressed concern that “[t]hese bills will reward those who have been irresponsible with users’ data and empower bad actors who would target consumers with malware, ransomware, and scams.”

The bills create an exception for otherwise prohibited actions which are “reasonably necessary” to protect safety, user privacy, security of nonpublic data, or the security of the covered platform. Apple’s letter principally takes issue with this exception, finding that it does not provide the company with enough leeway to innovate around privacy and security. The letter complains that “to introduce new and enhanced privacy or security protections under the bills, Apple would have to prove the protections were ‘necessary,’ ‘narrowly tailored,’ and that no less restrictive protections were available.” According to the letter, “[t]his is a nearly insurmountable test, especially when applied after-the-fact as an affirmative defense.” Of course, this is an overly broad statement­. The bills don’t subject all new privacy and security measures to this standard. Only the measures that are anticompetitive in the ways specifically spelled out by the bills are implicated. 

So what privacy and security measures would the bills prohibit? The letter is most concerned with the fact that the bills would restrain Apple from prohibiting “sideloading.” Sideloading refers to downloading an application onto, in this case, an Apple device, from somewhere other than the App Store. Lifting Apple’s restriction on the practice would allow developers to implement their own in-app payment systems and avoid the commission Apple takes (up to 30%) from app sales and in-app subscriptions and purchases. The theory is that prohibiting sideloading is anticompetitive in part because it results in higher prices for consumers. 

But Apple says that allowing sideloading would “put consumers in harm’s way because of the real risk of privacy and security breaches” sideloading causes. The letter further explains that sideloading allows developers to “circumvent[….] the privacy and security protections Apple has designed, including human review of every app and every app update.”

Are Apple’s Security Concerns Shared by All?

No. Privacy and security expert Bruce Schneier, who sits on the board of the Electronic Frontier Foundation and runs the security architecture at a data management company, wrote a rebuttal to Apple’s letter. According to Schneier, “[i]t’s simply not true that this legislation puts user privacy and security at risk” because “App stores monopolies cannot protect users from every risk, and they frequently prevent the distribution of important tools that actually enhance security.” Schneier thinks that “the alleged risks of third-party app stores and ‘sideloading’ apps pale in comparison to their benefits,” among them “encourag[ing] competition, prevent[ing] monopolist extortion, and guarantee[ing] users a new right to digital self-determination.”

Matt Stoller, who is the Director of Research at the American Economic Liberties Project, also wrote a strongly worded rebuttal. Like Schneier, Stoller seems to believe that Apple’s­ security-centric opposition to the bills is disingenuous. 

A New Angle on Consumer Welfare

Regardless of whether Apple’s concerns about privacy and security are overblown, the exchange between Apple, the drafters of the new antitrust bills, and members of the public is interesting because it engages with “consumer welfare”­–the entrenched legal standard which drives antitrust law­–in an atypical way.

Antitrust law exists primarily in common law, and the common law is the origin of the all-important consumer welfare standard. The standard is simple and has remained consistent since a seminal case from 1977. It is concerned primarily with whether a particular practice tends to decrease output and/or causes price to increase for consumers. If it does, the practice is anticompetitive and subject to injunction. While antitrust parties occasionally introduce other aspects of consumer welfare­­, such as the effects on innovation of a challenged practice, such effects are extremely difficult to prove in court. Therefore, most antitrust cases turn on price and output.

The bills in question implicitly take issue with the consumer welfare standard because they, in the language of the American Innovation and Choice Online Act, “provide that certain discriminatory conduct by covered platforms shall be unlawful.” Similarly, the Open App Markets Act seeks to “promote competition and reduce gatekeeper power in the app economy, increase choice, improve quality, and reduce costs for consumers.” By defining and prohibiting specific conduct outright, the bills circumvent the consumer welfare standard’s narrow focus on price and output and save potential antitrust plaintiffs from having to prove in court that Apple’s practices decrease output or increase price. 

Apple’s letter speaks the language of consumer welfare. It insists that “Apple offers consumers the choice of a platform protected from malicious and dangerous code. The bills eliminate that choice.” This point goes to the more traditional conception of consumer welfare in the antitrust context, i.e., proliferation of choice available to consumers. But primarily, the argument that Apple is making (however disingenuously) is that the bills “should be modified to strengthen­–not weaken–consumer welfare, especially with regard to consumer protection in the areas of privacy and security.” 

By focusing on “privacy and security” as a metric of consumer welfare in the antitrust context, Apple, legislators, and the general public are engaging in a conversation that ultimately expands the notion of consumer welfare beyond what would be borne out in a courtroom, constrained by entrenched antitrust precedent. In this way, the bills have already been productive. 

New Damages Trial for Apple and Samsung, Questions Still Left Unanswered

Picture1By Alex Hagel

Apple and Samsung are back! A new chapter in the Apple v. Samsung saga is set to begin in May.

A federal judge in California has scheduled a third trial since Apple’s initial suit in 2011. The suit alleges Samsung illegally copied several Apple design patents when designing its own phone. The new trial for the two tech giants follows the Supreme Court’s decision last year, which resulted in a (narrow) victory for Samsung.

This round of Apple v. Samsung involves three Apple design patents related to the front cover of its iPhones. Patent D618,577 covers “a black rectangular front face with rounded corners;” patent D593,087 covers “a rectangular front face with rounded corners and a raised rim;” and patent D604,305 covers “a grid of 16 colorful icons on a black screen.” WJLTA previously wrote about the peculiarities of design patents, and its distinction from the far more common utility patents.

Apple received a $1 billion verdict in 2012 after a jury found Samsung illegally used Apple’s design patents, and awarded Apple the entirety of Samsung’s profits from the sale of the infringing phones. Subsequent appeals affirmed the district court’s decision to award the full value of the phones, but that value was later recalculated to about $399 million.

On appeal to the Supreme Court, Samsung argued Apple was only entitled to the value of the relevant “article of manufacture,” rather than the value of the entire phone. During oral arguments, the parties struggled to articulate how and when an “article of manufacture” should be distinct from the entire product. The United States, as amicus, argued four factors should be considered:

  • the scope of the design claimed in the plaintiff’s patent, including the drawing and written description;
  • the relative prominence of the design within the product as a whole;
  • whether the design is conceptually distinct from the product as a whole; and
  • the physical relationship between the patented design and the rest of the product.

The unanimous opinion refused to adopt a specific test for determining what constitutes an article of manufacture, instead ruling “the term ‘article of manufacture’ is broad enough to encompass both a product sold to a consumer [i.e. an iPhone] as well as a component of that product [i.e. the front casing of an iPhone].”

Which brings us back to the new trial. In her order granting a new trial, the district court judge directed the parties to argue using the above factors articulated by the United States. Samsung will likely argue the front casing is an article of manufacture and thus distinct from the iPhone as a product, because (1) the design claimed in the plaintiff’s patent is limited to the front casing, rather than the entire phone, (2) the prominence of the front design is overshadowed by the capabilities of the iPhone as a “smartphone” (3) the product [a smartphone] is conceptually distinct from the patented “black rectangular front face with rounded corners” and (4) the front cover is separable from the rest of the phone.

This new trial will not likely be the end of the story. If the court accepts Samsung’s argument that the front casing is a distinct “article of manufacture,” any damages the court awards will likely only produce more litigation because there is no clear standard on how to value that “article of manufacture.”

Although valuing an article of manufacture was discussed during oral arguments at the Supreme Court, the justices did not decide the issue, and the district court judge has not offered guidance. The likely candidate, embraced by the government and Samsung at oral arguments, requires companies to use consumer surveys and data to deduce “to what extent people who bought the product did so because of the particular article of manufacture.” In the alternative, the court might adopt a test looking at the relative cost of developing a part and awarding damages in proportion. The court was hesitant to embrace this approach because of the potential for a “eureka!” moment, where an important component of the product is produced in a flash of genius, rather than through extensive research and development. This approach would necessarily value that important component much lower because of the low cost of production.

With this open question hanging over the court, this well-known saga is unlikely to end anytime soon.

Regulatory Landscape Remains Unclear for Mobile Health App Developers

8585047526_37a5bed3ff_bBy Mariko Kageyama

The digital health field has been growing exponentially and is now expanding rapidly into emerging markets. As a result, mobile health apps, or “mHealth apps,” have exploded in popularity. If you search for “health” on online app stores such as Apple’s App Store or Google Play, you will have no problem finding countless apps with various health-related purposes. One survey reports that nearly 260,000 mHealth apps were available worldwide by 2016.

However, what mHealth app developers and consumers may not realize is that these new technologies are becoming the target of increasingly tight regulations by both federal and state laws in the United States.

At the federal level, mobile health apps may be scrutinized under the following federal agency laws:

  • Health Insurance Portability and Accountability Act (HIPAA) and HITECH Act – These acts regulate data privacy and security of health information. They are enforced by the U.S. Department of Health & Human Services’ Office for Civil Rights (OCR) and Office of the National Coordinator for Health Information Technology (ONC);
  • Food, Drug, and Cosmetic Act (FDCA) – This act allows the Food and Drug Administration (FDA) to regulate the safety and effectiveness of “medical devices;” and
  • Federal Trade Commission Act (FTC Act) – This act both creates the FTC and allows it to enforce and penalize deceptive or unfair business practices including false or misleading claims about apps’ performance.

Among these major agency players, the FDA has struggled the most with trying to adapt its existing regulatory framework to include and regulate mHealth apps.

For instance, the FDA can regulate “medical devices,” but what qualifies as a “medical device” under FDA law? According to its 2015 Guidanace, the FDA does not want to regulate every single smartphone app that tangentially relates to fitness or wellness. Instead, the FDA only wants to keep an eye on a small subset of apps called “mobile medical apps” that may pose moderate to high risks to a patient’s safety if the apps fail to work as intended. “Mobile medical apps” can either be those connected to existing medical devices already regulated by FDA, or those that “transform” mobile platforms into an FDA-regulated device.

The FDA explains that a mobile app “transforms” into a medical device when it uses attachments, display screens, or sensors, or when it uses a mobile platform’s built-in features such as light, vibrations, and camera to create functionalities similar to those of currently regulated devices. But the exact actions that constitute a “transformation” are not yet known and remain open to significant agency discretion.

Therefore, if you were to create a new mHealth app that “transforms” a mobile device, you may need to seek FDA approval for a specific medical device classification based on the level of safety risks it poses. The classes are ranked I, II, or III and any class of device can be subject to what is known as Premarket Notification 510(k).

In anticipation of ambiguities in this field, multiple federal agencies collaborated in 2016 to create the Mobile Health Apps Interactive Tool. What is unique about this user-friendly educational website is that it is clearly intended for IT developers, not healthcare professionals or general consumers.

State laws have also come into play. Earlier in 2017, the New York Attorney General settled with three mHealth app developers for state law violations over their misleading marketing and privacy practices. Those mHealth apps are: My Baby’s Beat–Prenatal Listener; Heart Rate Monitor & Pulse Tracker; and Cardiio-Heart Rate Monitor + 7 Minute Workout. As illustrated in the settlement documents, these apps do not look any more sophisticated than other similar apps, but the New York AG maintained that these cardiac rate monitors probably fall under FDA Class II medical devices. Such a classification means that these are higher risk devices than Class I and thus subject to greater regulatory controls. Although the investigation did not go further, these state cases show that mHealth app developers and manufacturers can be exposing themselves to large amounts of liability at the state level as well as the federal level.

Despite this heightened oversight, the current FDA Guidance is clearly nothing more than a temporary fix when much more is needed to address these issues in such a rapidly growing and changing field. Because Congress has a less-than-great track record of quickly enacting laws, the FDA and other relevant agencies should act swiftly to reevaluate these regulations in order to ensure consumer health and safety while simultaneously fostering innovation in this massively beneficial field.

Picture Source

$5.3 Million Settlement over “Find Friends” iOS Feature

Picture1By Kiran Jassal

Eight companies (Foodspotting, Foursquare, Gowalla, Instagram, Kik, Path, Twitter, and Yelp) have agreed to a proposed settlement of $5.3 million in a case surrounding the “Find Friends” feature in iOS apps. As the name suggests, “Find Friends” allows consumers to quickly discover if any of their contacts are also using an app. Interestingly, both Apple and LinkedIn are among the companies named in the lawsuit; however, they are continuing to fight the case while the aforementioned entities have decided to settle. Continue reading

Design Patents Taking Center Stage in IP Litigation

Center Stage.pngBy Toban Platt

In Apple v. Samsung, the Federal Circuit court of appeals showed how valuable a design patent can be by affirming the trial court’s award for over $500 million dollars to Apple based largely on its design patents. This decision put design patents in the spotlight of intellectual property protection. The case first started in 2012 and revolved around design patents on particulars of Apple phones, including D618,577 (black rectangle with rounded corners), D593,087 (bezel on surrounding rim), and D604,305 (colorful grid of 16 icons). Apple was able to show that several Samsung phones were substantially similar to the iPhone, which included the design patents at issue. The court found this entitled Apple to collect all of the profits Samsung had made from its infringing phones.

Continue reading