throbber
Case 3:22-cv-02746-JD Document 93 Filed 11/17/22 Page 1 of 20
`
`Paul J. Riehle (SBN 115199)
`paul.riehle@faegredrinker.com
`FAEGRE DRINKER BIDDLE & REATH
`LLP
`Four Embarcadero Center, 27th Floor
`San Francisco, CA 94111
`Telephone: (415) 591-7500
`
`Douglas J. Dixon (SBN 275389)
`ddixon@hueston.com
`HUESTON HENNIGAN LLP
`620 Newport Center Drive, Suite 1300
`Newport Beach, CA 92660
`Telephone: (949) 229-8640
`
`Counsel for Plaintiffs Match Group, LLC, et al.
`
`Christine A. Varney (pro hac vice)
`cvarney@cravath.com
`CRAVATH, SWAINE & MOORE LLP
`825 Eighth Avenue
`New York, New York 10019
`Telephone: (212) 474-1000
`
`Counsel for Plaintiff Epic Games, Inc.
`
`[Additional Counsel Appear on Signature
`Page]
`
`UNITED STATES DISTRICT COURT
`
`NORTHERN DISTRICT OF CALIFORNIA
`
`SAN FRANCISCO DIVISION
`
`IN RE GOOGLE PLAY STORE
`ANTITRUST LITIGATION
`
`THIS DOCUMENT RELATES TO:
`
`Epic Games Inc. v. Google LLC et al.,
`Case No. 3:20-cv-05671-JD
`
`Match Group, LLC et al. v. Google LLC et al.,
`Case No. 3:22-cv-02746-JD
`
` Case No. 3:21-md-02981-JD
`
`EPIC’S AND MATCH’S NOTICE OF
`MOTION AND MOTION TO AMEND
`COMPLAINTS
`
`Date: November 17, 2022 at 10:00 a.m.
`Courtroom: 11, 19th Floor
`Judge: Hon. James Donato
`
`EPIC’S AND MATCH’S NOTICE OF MOTION AND MOTION TO AMEND COMPLAINTS
`Case No. 3:21-md-02981-JD
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`

`

`Case 3:22-cv-02746-JD Document 93 Filed 11/17/22 Page 2 of 20
`
`
`
`TO ALL PARTIES HEREIN AND THEIR ATTORNEYS OF RECORD:
`
`PLEASE TAKE NOTICE that on November 17, 2022, at 10:00 a.m., or as soon
`
`thereafter as the matter may be heard, in the United States District Court for the
`
`Northern District of California, before the Honorable James Donato, Plaintiff Epic
`
`Games, Inc. (“Epic”) and Plaintiffs Match Group LLC, Humor Rainbow, Inc.,
`
`PlentyofFish Media ULC, and People Media, Inc., (“Match”) will and hereby do move
`
`for an order granting Epic and Match leave to file their proposed amended complaints
`
`(“Proposed Amended Complaints,” which are submitted with this motion as Exhibits A
`
`and K) and ordering that the Proposed Amended Complaints be deemed filed. This
`
`motion is made pursuant to Federal Rule of Civil Procedure (“FRCP”) 15 on the
`
`grounds that granting this motion will not result in prejudice, the motion is neither futile
`
`nor legally insufficient, Epic and Match bring this motion without undue delay, and
`
`Epic and Match are not seeking leave to amend in bad faith. In addition, this motion is
`
`made pursuant to FRCP 16 on the ground that there is good cause to modify the Second
`
`Amended MDL Scheduling Order for the limited purpose of permitting Epic and Match
`
`to file their Proposed Amended Complaints. This motion is based upon this Notice of
`
`Motion and Motion, the accompanying Memorandum of Points and Authorities, the
`
`Proposed Amended Complaints, Declaration of Michael J. Zaken (the “Zaken Decl.”)
`
`and [Proposed] Order, as well as all matters with respect to which this Court may take
`
`judicial notice, and such oral and documentary evidence as properly may be presented
`
`to the Court.
`
`STATEMENT OF RELIEF SOUGHT
`
`Epic and Match seek an Order granting their request to allow Epic and Match to
`
`file their Proposed Amended Complaints pursuant to FRCP Rule 15 and amend the
`
`Second Amended MDL Scheduling Order for the limited purpose of allowing Epic and
`
`Match to do so.
`
`EPIC’S AND MATCH’S NOTICE OF MOTION AND MOTION TO AMEND COMPLAINTS
`Case No.: 3:21-md-02981-JD
`
`i
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`

`

`Case 3:22-cv-02746-JD Document 93 Filed 11/17/22 Page 3 of 20
`
`
`
`Table of Contents
`
`Page
`
`Table of Authorities .....................................................................................................iii
`
`MEMORANDUM OF POINTS AND AUTHORITIES ................................................ 1
`
`I.
`
`INTRODUCTION .............................................................................................. 1
`
`II.
`
`BACKGROUND ................................................................................................ 3
`
`III. LEGAL STANDARD ......................................................................................... 6
`
`IV. ARGUMENT...................................................................................................... 7
`
`A.
`
`The Proposed Amendments Should Be Allowed Under Rule 15. .............. 7
`
`i.
`
`ii.
`
`iii.
`
`iv.
`
`The Amendments Will Not Prejudice Google. ................................ 8
`
`Epic and Match Have Not Unduly Delayed. ................................. 10
`
`Epic and Match Seek To Amend in Good Faith. ........................... 10
`
`The Proposed Amendments Are Not Futile. .................................. 11
`
`B.
`
`There Is Good Cause To Amend the Scheduling Order. .......................... 11
`
`V.
`
`CONCLUSION ................................................................................................ 12
`
`
`
`
`
`
`
`EPIC’S AND MATCH’S NOTICE OF MOTION AND MOTION TO AMEND COMPLAINTS
`Case No.: 3:21-md-02981-JD
`
`ii
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`

`

`Case 3:22-cv-02746-JD Document 93 Filed 11/17/22 Page 4 of 20
`
`Table of Authorities
`
`
`
`Page(s)
`
`
`
`
`
`Cases
`
`Allen v. Bayshore Mall, No. 12-CV-02368-JST, 2013 WL 6441504 (N.D. Cal.
`
`Dec. 9, 2013) ........................................................................................................... 11
`
`Avago Techs. Fiber IP (Singapore) Pte. Ltd. v. IPtronics Inc., No. 5:10-CV-
`
`02863-EJD, 2012 WL 3835107 (N.D. Cal. Sept. 4, 2012).......................................... 9
`
`Clarke v. Upton, 703 F. Supp. 2d 1037 (E.D. Cal. 2010) .............................................. 11
`
`Cont’l Cas. Co. v. United States, No. 02-5292 VRW, 2005 WL 8162326 (N.D.
`
`Cal. June 22, 2005) .................................................................................................... 7
`
`Foman v. Davis, 371 U.S. 178 (1962) ....................................................................... 6, 11
`
`Griggs v. Pace Am. Grp., 170 F.3d 877 (9th Cir. 1999) .................................................. 6
`
`Howey v. United States, 481 F.2d 1187 (9th Cir. 1973)......................................... 6, 7, 10
`
`Hurn v. Retirement Fund Trust of Plumbing, Heating & Piping Indus. of S.
`
`California, 648 F2d 1252 (9th Cir. 1981) ................................................................... 7
`
`In re Intuitive Surgical Sec. Litig., No. 5:13-CV-01920-EJD, 2017 WL 363269
`
`(N.D. Cal. Jan. 25, 2017) ......................................................................................... 10
`
`Johnson v. Mammoth Recreations, Inc., 975 F.2d 604 (9th Cir. 1992) ............................ 7
`
`Lockheed Martin Corp. v. Network Sols., 194 F.3d 980 (9th Cir. 1999) .......................... 9
`
`Oracle Am., Inc. v. Hewlett Packard Enter. Co., No. 16-CV-01393-JST, 2017
`
`WL 3149297 (N.D. Cal. July 25, 2017) ........................................................... 8, 9, 11
`
`Owens v. Kaiser Found. Health Plan, Inc., 244 F.3d 708 (9th Cir. 2001) ....................... 6
`
`Sonoma Cty. Ass’n of Retired Employees v. Sonoma Cty., 708 F.3d 1109 (9th
`
`Cir. 2013)........................................................................................................... 6, 8, 9
`
`Stearns v. Select Comfort Retail Corp., 763 F. Supp. 2d 1128 (N.D. Cal. 2010) ............. 9
`
`EPIC’S AND MATCH’S NOTICE OF MOTION AND MOTION TO AMEND COMPLAINTS
`Case No.: 3:21-md-02981-JD
`
`iii
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`

`

`Case 3:22-cv-02746-JD Document 93 Filed 11/17/22 Page 5 of 20
`
`
`
`
`Trans Bay Cable LLC v. M/V Ocean Life, No. 14-cv-04854-JD, 2015 WL
`
`7075618 (N.D. Cal. Nov. 13, 2015) ........................................................................... 7
`
`Vigil v. Coloplast Corp., No. 319-CV-01851-GPC-BGS, 2020 WL 94378
`
`(S.D. Cal. Jan. 8, 2020) .................................................................................... 8, 9, 10
`
`Waldrip v. Hall, 548 F.3d 729 (9th Cir. 2008) ................................................................ 6
`
`Statutes & Rules
`
`Fed. R. Civ. P. 15(a)(2) ................................................................................................... 6
`
`Fed. R. Civ. P. 16(b)(4) ................................................................................................... 7
`
`
`
`
`
`EPIC’S AND MATCH’S NOTICE OF MOTION AND MOTION TO AMEND COMPLAINTS
`Case No.: 3:21-md-02981-JD
`
`iv
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`

`

`Case 3:22-cv-02746-JD Document 93 Filed 11/17/22 Page 6 of 20
`
`
`
`I.
`
`MEMORANDUM OF POINTS AND AUTHORITIES
`
`INTRODUCTION
`
`Epic and Match seek leave to amend their Complaints to add two counts against
`
`Defendants Google LLC, Google Ireland Limited, Google Commerce Limited and
`
`Google Asia Pacific Pte. Limited (collectively, “Google”). The new counts arise out of
`
`anticompetitive agreements between Google and app developers that were
`
`contemplating the launch of competing Android app stores or distributing their apps
`
`outside of Google Play. Some of these agreements were intended to, and did, stop
`
`developers from launching competing app stores, which is a per se violation of the
`
`antitrust laws. Other agreements were intended to, and did, unlawfully stop developers
`
`from making Android apps and other unique content available outside Google Play.
`
`Google has been on notice of Epic’s and Match’s claims regarding these agreements for
`
`months; they have been the subject of extensive discovery and the subject of filings in
`
`this Court. The proposed amendments reflected in the attached Proposed Amended
`
`Complaints simply conform Epic’s and Match’s claims to evidence obtained through
`
`discovery. The amendments will also facilitate a clear charge to the jury.
`
`Epic and Match already allege that Google entered into anticompetitive
`
`agreements with developers and OEMs that unreasonably restrict competition in the
`
`Android App Distribution Market, in violation of Sections 1 and 2 of the Sherman Act.
`
`(See, e.g., Epic’s First Amended Complaint (“FAC”) ¶¶ 6, 33, 98, 119, 128, 188-95,
`
`233-43, MDL Dkt. No. 64.) Epic and Match now merely seek to add two counts
`
`asserting that certain of Google’s agreements with developers are standalone violations
`
`of Section 1 of the Sherman Act, including per se violations based on horizontal
`
`agreements that prevented developers from proceeding with concrete plans to launch
`
`competing app stores. Specifically, the Proposed Amended Complaints allege that
`
`Google has paid off app developers with the means, capability and desire to enter the
`
`Android App Distribution Market (1) not to launch competing Android app stores, and
`
`(2) to give up the ability to distribute differentiating content—like exclusive and early-
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`EPIC’S AND MATCH’S NOTICE OF MOTION AND MOTION TO AMEND COMPLAINTS
`Case No.: 3:21-md-02981-JD
`
`

`

`Case 3:22-cv-02746-JD Document 93 Filed 11/17/22 Page 7 of 20
`
`
`
`release games—anywhere other than on Google Play. By breaking this conduct into
`
`separate counts, the Proposed Amended Complaints will facilitate a clear charge to the
`
`jury on these agreements.
`
`Google will not be prejudiced by the Proposed Amended Complaints. Because
`
`the new counts relate exclusively to Google’s conduct and agreements, Google has the
`
`information it needs to mount a defense. Further, Google has long been on notice of
`
`Epic’s and Match’s position regarding these agreements. For example, on April 28,
`
`2022, Epic filed a Motion for Preliminary Injunction in which it alleged, under the
`
`heading “Google Paid Top App Developers Not To Compete”, that Google entered into
`
`deals with developers that “could, in fact . . . establish and launch their own app store on
`
`Android”, which “deprived developers of any incentive to launch their own store”.
`
`(MDL Dkt. No. 213 at 10.) A month later, on May 27, 2022, Plaintiffs Epic, Consumer
`
`Plaintiffs, and State Attorneys General Plaintiffs (“Plaintiff States”) filed a joint
`
`discovery letter with Activision Blizzard, Inc. (“ABK”) seeking to compel the testimony
`
`of ABK’s CFO, Armin Zerza, and asserting that “[o]ne of Plaintiffs’ central claims is
`
`that Google systematically executed agreements with potential competitors to stifle
`
`competition . . . Google paid companies not to launch competing app stores.” (MDL
`
`Dkt. No. 259.) Since then, deposition testimony taken as recently as September 22,
`
`2022 has crystalized the nature and scope of these agreements, highlighting the
`
`importance in clearly enumerating the counts in Epic’s and Match’s Complaints.
`
`The amendments will not prejudice Google where they conform the counts to
`
`allegations that have been litigated for months, rely on information that Google was
`
`fully aware of, and have been fully explored via extensive discovery by all Parties,1
`
`including Google. Epic and Match therefore respectfully request that the Court allow
`
`Epic and Match to amend their Complaints to conform their claims against Google to
`
`the evidence developed during discovery.
`
`
`1“Parties” refers to Epic, Consumer Plaintiffs, Plaintiff States, Match (collectively
`“Plaintiffs”) and Google.
`EPIC’S AND MATCH’S NOTICE OF MOTION AND MOTION TO AMEND COMPLAINTS
`Case No.: 3:21-md-02981-JD
`2
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`

`

`Case 3:22-cv-02746-JD Document 93 Filed 11/17/22 Page 8 of 20
`
`
`
`II. BACKGROUND
`
`Epic filed its Complaint on August 13, 2020 and its FAC on July 21, 2021. (Epic
`
`Dkt. 1, MDL Dkt. No. 64.) Match filed its initial complaint (together with Epic’s FAC,
`
`“Complaints”) on May 9, 2022. (Match Dkt. 1.) On October 22, 2021, the Court
`
`entered the MDL Scheduling Order providing that the last date to add parties and amend
`
`the pleadings would be December 3, 2021.2 (MDL Dkt. No. 122.) Since that date,
`
`however, Google and multiple third parties produced hundreds of thousands of
`
`documents; Plaintiffs have taken all but one of the 32 depositions of Google witnesses
`
`(with three more outstanding); and the Parties took 10 depositions of third-party
`
`witnesses. (Zaken Decl. ¶ 16.) In short, the current evidentiary record in this case is
`
`vastly more developed than it was in early December 2021.
`
`Google has been on notice of Epic’s and Match’s intent to challenge Google’s
`
`agreements with top developers as anticompetitive since at least the filing of Epic’s
`
`FAC last summer. The general contours of “Project Hug”—Google’s plan to eliminate
`
`game developers’ agitation and competitive threat to distribute outside of Play—are
`
`addressed in Epic’s FAC. (See, e.g., Epic’s FAC ¶¶ 119, 128.) Throughout discovery,
`
`Epic and Match sought documents and deposition testimony about these arrangements.
`
`For example, after the December 3, 2021 amendment deadline, Google produced
`
`documents showing that Google entered into its Project Hug deal with ABK, with the
`
`understanding that “[i]f this deal falls through, [Mr. Zerza] claims that [ABK] will
`
`launch [its] own mobile distribution platform”. (Zaken Decl. Ex. C, GOOG-PLAY-
`
`007280918.) Likewise, after the December 3, 2021 amendment deadline, Google
`
`produced documents and provided testimony showing that Google paid an eight-figure
`
`sum to Riot, another developer that “specifically told Google that they were considering
`
`starting their own competing Android app store[]” (Id. at Ex. H, Koh Tr. 200:4-10), in
`
`
`2On October 5, 2022, the Court entered the Second Amended MDL Scheduling Order
`(MDL Dkt. No. 338), the operative scheduling order, which states that the date to add
`parties and amend pleadings has closed.
`EPIC’S AND MATCH’S NOTICE OF MOTION AND MOTION TO AMEND COMPLAINTS
`Case No.: 3:21-md-02981-JD
`3
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`

`

`Case 3:22-cv-02746-JD Document 93 Filed 11/17/22 Page 9 of 20
`
`
`
`order “to get Riot to stop their inhouse ‘app store’ efforts and bring their billion dollar
`
`League of Legends franchise and other mobile games to Play”. (Id. at Ex. D, GOOG-
`
`PLAY-007424789 and Ex. E, GOOG-PLAY-000929031.) Plaintiffs have also
`
`questioned Google and third-party witnesses in Rule 30(b)(1) and 30(b)(6) capacities
`
`about the company’s deals with top developers, including specifically its Hug deals, in
`
`the depositions of Paul Bankhead, Paul Feng, Paul Gennai, Donald Harrison, Hiroshi
`
`Lockheimer, Lawrence Koh, James Kolotouros, Michael Marchak, Ruth Porat and
`
`Jamie Rosenberg. (Id. at ¶ 17.)
`
`Crucial portions of the discovery into Google’s deals with developers were
`
`completed in late August and late September 2022, with the deposition of Ms. Purnima
`
`Kochikar, Vice President of Google Play Partnerships,3 and the compelled
`
`September 22, 2022 deposition of Mr. Zerza, the CFO of ABK, the recipient of
`
`Google’s largest Hug deal.4 (Id. at Ex. F, GOOG-PLAY-007847561 and Ex. G,
`
`GOOG-PLAY-007273439.) For example, Ms. Kochikar testified on August 31, 2022
`
`that Google’s deal with ABK was discussed in the context of ABK launching an
`
`alternative app store that could lead other developers to similarly seek to launch other
`
`stores or to distribute through ABK’s store, and that it was Google’s understanding that
`
`if ABK accepted its “bespoke” Hug deal, it would cease investment in its rival store.
`
`(Id. at Ex. I, Kochikar Tr. at 139:8-140:5.) Similarly, Ms. Kochikar testified that
`
`Google pursued and signed a Hug deal with Riot, which presented “risks” to Google
`
`because of its plans to launch a game outside of Play. (Id. at Ex. I, Kochikar Tr. at
`
`
`3Ms. Kochikar’s deposition was rescheduled several times at Google’s request due to
`scheduling and other conflicts. Ms. Kochikar was Google’s 30(b)(6) representative
`designated to testify about certain of Google’s contracts with developers, including its
`communications and negotiations with ABK and efforts to “maintain Android
`Developer satisfaction”, such as its Hug deals. (Zaken Decl. Ex. I, Kochikar Tr. at 19:6-
`20:23 (Day 1); Plaintiffs’ Rule 30(b)(6) Notice of Deposition of Defendants.)
`4Plaintiffs sought to depose Mr. Zerza earlier in the case, but ABK opposed that
`effort, requiring that Plaintiffs seek relief from the Court before being able to do so.
`(See MDL Dkt. Nos. 259 and 321.)
`EPIC’S AND MATCH’S NOTICE OF MOTION AND MOTION TO AMEND COMPLAINTS
`Case No.: 3:21-md-02981-JD
`4
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`

`

`Case 3:22-cv-02746-JD Document 93 Filed 11/17/22 Page 10 of 20
`
`
`
`145:2-11.) Ms. Kochikar admitted she wrote in a document that Google “pulled all the
`
`stops” to prevent Riot from launching “their inhouse ‘app store’ efforts”, including
`
`offering Riot a deal for $10 million in co-marketing benefits on top of their Hug deal,
`
`and that Riot did not launch an app store. (Id. at Ex. I, Kochikar Tr. at 148:1-150:23.)
`
`And Mr. Zerza testified that in December 2019, prior to entering into the Hug deal,
`
`ABK was actively exploring building its own store with the “expectation” that its store
`
`would have “better economics” than distribution through Google Play. (Id. at Ex. J,
`
`Zerza Tr. at 105:24-112:12.) However, ABK decided not to launch the store after ABK
`
`secured its Hug deal with Google, which promised ABK over $300 million in benefits.
`
`(Id.) At present, ABK still does not have its own Android distribution or payment
`
`system. (Id. at Ex. J, Zerza Tr. at 71:25-72:7.)
`
`Given the continuing development of the facts surrounding Google’s conduct, it
`
`did not make sense for Epic and Match to update their Complaints before Ms.
`
`Kochikar’s and Mr. Zerza’s depositions. However, Epic and Match did make their view
`
`of the Project Hug agreements and their implications for the case clear to Google,
`
`including in several court filings and throughout discovery. For example, in Epic’s
`
`Motion for a Preliminary Injunction, Epic asserted that Google “pa[id] off top app
`
`developers to stop them from developing and launching competing Android app stores”;
`
`that “Google spent a billion dollars on secret deals with the top app developers that . . .
`
`could, in fact, come up with the infrastructure needed to actually establish and launch
`
`their own app store on Android . . . [and] systematically deprived developers of any
`
`incentive to launch their own stores or to partner with other nascent stores on Android”;
`
`and that “Activision was prepared and threatening to launch a competing app store on
`
`Android. . . [but] Google executed its Project Hug agreement with Activision, under
`
`which Google agreed to pay Activision $360 million over three years . . . [and]
`
`Activision abandoned its plans to launch a competing Android app store”. (MDL Dkt.
`
`No. 213 at 9-10.) In late May 2022, Epic, Consumer Plaintiffs, and Plaintiff States filed
`
`EPIC’S AND MATCH’S NOTICE OF MOTION AND MOTION TO AMEND COMPLAINTS
`Case No.: 3:21-md-02981-JD
`5
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`

`

`Case 3:22-cv-02746-JD Document 93 Filed 11/17/22 Page 11 of 20
`
`
`
`a joint discovery letter brief regarding the deposition of ABK CFO Mr. Zerza (MDL
`
`Dkt. No. 259) in which they stated that:
`
`“Google paid companies not to launch competing app stores.
`Specifically, discovery in this case has revealed that
`Activision planned to leverage its popular app catalog to
`launch a mobile app store that would directly compete with
`the Google Play Store, but that Activision abandoned those
`plans in exchange for several hundred million dollars in
`consideration from Google.” (Id. at 4).
`
`Epic spoke with Google about its intention to amend its FAC on September 30,
`
`2022 and shared a draft of its SAC with Google two days later, on October 2, 2022.
`
`(Zaken Decl. at ¶ 19.) Google informed Epic on October 7, 2022 that it did not consent
`
`to allow Epic to amend its FAC. (Id.) The same day, Epic informed Google that Match
`
`intended to join in this motion and file a similar amendment. (Id.)
`III. LEGAL STANDARD
`
`This motion to amend is governed by Federal Rule of Civil Procedure 15, which
`
`directs that “[t]he court should freely give leave [to amend] when justice so requires”.
`
`Fed. R. Civ. P. 15(a)(2). “[T]his mandate is to be heeded”, Foman v. Davis, 371 U.S.
`
`178, 182 (1962), and “[t]he policy of allowing amendments ‘is to be applied with
`
`extreme liberality’”, Waldrip v. Hall, 548 F.3d 729, 732 (9th Cir. 2008) (quoting
`
`Owens v. Kaiser Found. Health Plan, Inc., 244 F.3d 708, 712 (9th Cir. 2001)). “A
`
`district court determines the propriety of a motion to amend by ascertaining the presence
`
`of any of four factors: bad faith, undue delay, prejudice to the opposing party and/or
`
`futility.” Griggs v. Pace Am. Grp., 170 F.3d 877, 881 (9th Cir. 1999). The Ninth
`
`Circuit has held that courts may decline to grant leave to amend for one or more of these
`
`reasons “only if there is strong evidence.” Sonoma County Ass’n of Retired
`
`Employees v. Sonoma County, 708 F3d 1109, 1117 (9th Cir. 2013). “While all these
`
`factors are relevant, the crucial factor is the resulting prejudice to the opposing party.”
`
`Howey v. United States, 481 F.2d 1187, 1190 (9th Cir. 1973). The Ninth Circuit and
`
`EPIC’S AND MATCH’S NOTICE OF MOTION AND MOTION TO AMEND COMPLAINTS
`Case No.: 3:21-md-02981-JD
`6
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`

`

`Case 3:22-cv-02746-JD Document 93 Filed 11/17/22 Page 12 of 20
`
`
`
`California district courts have consistently held that “[w]here there is lack of prejudice
`
`to the opposing party and the amended complaint is obviously not frivolous or made as
`
`a dilatory maneuver in bad faith, it is an abuse of discretion to deny such a motion.”
`
`Cont’l Cas. Co. v. United States, No. 02-5292 VRW, 2005 WL 8162326, at *4 (N.D.
`
`Cal. June 22, 2005) (citing Howey, 481 F2d at 1190-91). Further, “delay alone does not
`
`provide sufficient grounds for denying leave to amend.” Id. (citing Hurn v. Retirement
`
`Fund Trust of Plumbing, Heating & Piping Indus. of S. California, 648 F2d 1252, 1254
`
`(9th Cir. 1981)).
`
`While Federal Rule of Civil Procedure 15(a) governs a motion to amend
`
`pleadings to add claims or parties, as a procedural matter Rule 16 also applies where, as
`
`here, the request to amend is filed after the scheduling order deadline for amendments
`
`has passed. Johnson v. Mammoth Recreations, Inc., 975 F.2d 604, 607–08 (9th Cir.
`
`1992). Federal Rule of Civil Procedure 16(b)(4) requires a showing of good cause and
`
`the Court’s consent in order to amend a scheduling order. The good cause inquiry
`
`focuses primarily on “the diligence of the party seeking the amendment” and “the
`
`moving party’s reasons for seeking modification.” Johnson, 975 F.2d at 609. The
`
`Court has broad discretion to modify a scheduling order to allow an amendment to the
`
`pleadings. Id. at 607-08. This Court has found good cause to permit amendment where
`
`doing so would prevent a future “preclusion or waiver argument . . . on purely technical
`
`and formalistic grounds”. Trans Bay Cable LLC v. M/V Ocean Life, No. 14-cv-04854-
`
`JD, 2015 WL 7075618, at *1-2 (N.D. Cal. Nov. 13, 2015).
`IV. ARGUMENT
`A. The Proposed Amendments Should Be Allowed Under Rule 15.
`
`This Court should allow Epic and Match to file the Proposed Amended
`
`Complaints because each of the four factors courts assess under Rule 15 weigh in favor
`
`of allowing amendment. First, the amendments cause no prejudice to Google because
`
`the Proposed Amended Complaints serve only to conform Epic’s and Match’s counts to
`
`the record developed through discovery, Google has been on notice that Epic and Match
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`EPIC’S AND MATCH’S NOTICE OF MOTION AND MOTION TO AMEND COMPLAINTS
`Case No.: 3:21-md-02981-JD
`7
`
`

`

`Case 3:22-cv-02746-JD Document 93 Filed 11/17/22 Page 13 of 20
`
`
`
`were challenging the Project Hug agreements with developers, Google was fully aware
`
`of Epic’s and Match’s theory of liability, and Google had ample opportunity to (and did)
`
`take discovery regarding these issues. Second, Epic and Match did not unduly delay
`
`because they sought leave promptly after obtaining information in key depositions, and
`
`long before dispositive motion practice and trial. Third, this proposal to amend is not
`
`made in bad faith. Finally, adding these claims to Epic’s and Match’s Complaints will
`
`not be futile.
`i.
`
`The Amendments Will Not Prejudice Google.
`
`“To overcome Rule 15(a)’s liberal policy with respect to the amendment of
`
`pleadings, a showing of prejudice must be substantial.” See Oracle Am., Inc. v. Hewlett
`
`Packard Enter. Co., No. 16-CV-01393-JST, 2017 WL 3149297, at *3 (N.D. Cal.
`
`July 25, 2017) (citation omitted). Substantial prejudice will not be shown where a
`
`plaintiff’s “main claims and legal theories remain the same” or where a non-moving
`
`party is “fully prepared to litigate the substantive issue of the claim, given that both the
`
`theory and the operative facts of the claim remain the same.” Id. at *4 (citing Sonoma
`
`Cty., 708 F.3d at 1118). This is especially the case where amendment comes many
`
`months prior to dispositive motion practice and the final pre-trial conference. See
`
`Vigil v. Coloplast Corp., No. 319-CV-01851-GPC-BGS, 2020 WL 94378, at *3 (S.D.
`
`Cal. Jan. 8, 2020).
`
`The Proposed Amended Complaints cause no prejudice to Google because
`
`Google was aware that Epic and Match were challenging Google’s anticompetitive
`
`agreements with developers and developing the record with respect to these agreements
`
`through discovery. The only change introduced by the amendments is that, while the
`
`Complaints described these agreements as aggravating the effects of other agreements
`
`Google had with OEMs, the Proposed Amended Complaints break out Google’s
`
`agreements with developers as sufficiently egregious to be violative of the antitrust laws
`
`in and of themselves—and, in certain instances, to be violative per se. The evidence to
`
`support these claims was developed through discovery and, as noted above, raised in
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`EPIC’S AND MATCH’S NOTICE OF MOTION AND MOTION TO AMEND COMPLAINTS
`Case No.: 3:21-md-02981-JD
`8
`
`

`

`Case 3:22-cv-02746-JD Document 93 Filed 11/17/22 Page 14 of 20
`
`
`
`Epic’s Motion for a Preliminary Injunction (MDL Dkt. No. 213 at 9-10) and Plaintiffs’
`
`joint discovery letter brief regarding the deposition of ABK CFO Mr. Zerza (MDL Dkt.
`
`No. 259 at 4-5). Epic and Match now seek to conform their counts against Google to
`
`the record evidence, based on discovery (which Google has always had in its
`
`possession) that has crystalized the scope and nature of Google’s anticompetitive
`
`agreements with developers, and in particular, demonstrated that per se claims are
`
`appropriate. As such, the Proposed Amended Complaints should come as no surprise
`
`to, let alone prejudice, Google. See Sonoma, 708 F.3d at 1118 (finding no prejudice
`
`where the defendant was already prepared to litigate the same facts and issues brought
`
`under similar claims); Oracle, 2017 WL 3149297, at *3.
`
`Further, the Proposed Amended Complaints will not prejudice Google’s ability to
`
`adequately prepare a defense or impact this case’s forward progress. Discovery and
`
`motion practice have fully adduced the relevant facts underlying the proposed claims, so
`
`that no additional discovery and no delay to the schedule is warranted.5 Google has
`
`adequate time to address the limited amendments in its expert disclosures, dispositive
`
`motion practice and at trial—in part because these issues have already been at play in
`
`the case for many months. The Proposed Amended Complaints will not prejudice
`
`Google’s ability to adequately prepare a defense or delay resolution of this matter. See
`
`Vigil, 2020 WL 94378, at *3.
`
`
`5Even if additional discovery were necessary (it is not), the prospect of additional
`discovery alone would not constitute undue prejudice. While “[a] need to reopen
`discovery and therefore delay the proceedings supports a district court’s finding of
`prejudice from a delayed motion to amend the complaint”, Lockheed Martin Corp. v.
`Network Sols., 194 F.3d 980, 986 (9th Cir. 1999), “[n]either delay resulting from the
`proposed amendment nor the prospect of additional discovery needed by the non-
`moving party in itself constitutes a sufficient showing of prejudice”, Stearns v. Select
`Comfort Retail Corp., 763 F. Supp. 2d 1128, 1158 (N.D. Cal. 2010). See Avago Techs.
`Fiber IP (Singapore) Pte. Ltd. v. IPtronics Inc., No. 5:10-CV-02863-EJD, 2012 WL
`3835107, at *3 (N.D. Cal. Sept. 4, 2012) (delay and the expenses incurred in responding
`to new claims do not constitute undue prejudice without some credible showing of
`unfairness).
`EPIC’S AND MATCH’S NOTICE OF MOTION AND MOTION TO AMEND COMPLAINTS
`Case No.: 3:21-md-02981-JD
`9
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`

`

`Case 3:22-cv-02746-JD Document 93 Filed 11/17/22 Page 15 of 20
`
`
`
`ii.
`
`Epic and Match Have Not Unduly Delayed.
`
`Epic and Match are seeking to amend their Complaints in light of information
`
`made available through discovery. It would not have been possible to do this on
`
`December 3, 2021, as discovery on this issue was just beginning, and Match had not yet
`
`filed suit. As the discovery record developed, Epic and Match repeatedly made known
`
`that they believed certain of Google’s agreements with developers were agreements not
`
`to compete in Android app distribution. Epic and Match now seek to add specific
`
`counts on which to instruct the jury since obtaining additional confirming information at
`
`key depositions that did not occur until August and September 2022 due to the Google
`
`witness’s schedule and ABK’s opposition to its witness being deposed. There has been
`
`no undu

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket