Express Mobile, Inc. v. GoDaddy.com, LLC

CourtDistrict Court, D. Delaware
DecidedJuly 5, 2023
Docket1:19-cv-01937
StatusUnknown

This text of Express Mobile, Inc. v. GoDaddy.com, LLC (Express Mobile, Inc. v. GoDaddy.com, LLC) is published on Counsel Stack Legal Research, covering District Court, D. Delaware primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Express Mobile, Inc. v. GoDaddy.com, LLC, (D. Del. 2023).

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF DELAWARE

EXPRESS MOBILE, INC., ) ) Plaintiff, ) ) vs. ) Civil Action No. 1:19-cv-01937-MFK ) GODADDY.COM, LLC, ) ) Defendant. )

MEMORANDUM OPINION AND ORDER MATTHEW F. KENNELLY, District Judge: Express Mobile, Inc. sued GoDaddy.com, LLC alleging that two of GoDaddy's products—Website Builder (WSB) and Managed WordPress (MWP)—willfully infringe numerous claims of certain patents owned by Express Mobile that are directed to tools for displaying content on mobile devices.1 Express Mobile's claims went to a jury trial in late February 2023. In addition to asserting a defense of non-infringement, GoDaddy contended that Express Mobile's patents were invalid. The jury found in GoDaddy's favor on the question of infringement and willfulness but found in favor of Express Mobile on the question of invalidity. Because it found in favor of GoDaddy on the question of infringement, the jury awarded Express Mobile no damages. After the close of GoDaddy's case in chief, Express Mobile moved for judgment as a matter of law under Federal Rule of Civil Procedure Rule 50(a). The Court took the motion under advisement. Express Mobile has now renewed its Rule 50 motion and

1 Express Mobile contends that GoDaddy's WSB and MWP products infringe claims 1, 3, 12, 16, and 22 of U.S. Patent No. 9,063,755 (the '755 patent); claims 1 and 13 of U.S. Patent No. 9,471,287 (the '287 patent); and claims 1, 11, 13, 17, and 19 of U.S. Patent No. 9,928,044 (the '044 patent). has also moved for a new trial under Federal Rule of Civil Procedure 59(a). For the reasons set forth below, the Court denies both motions. Background The Court assumes familiarity with this case's factual and procedural

background, which the Court has discussed in prior written opinions. The following background is relevant to the post-trial motions and largely is taken from the Court's summary judgment decision. A. The asserted patents The asserted patents relate to two concepts that allow web designers to integrate third-party web services into their websites. The patents disclose an authoring tool that generates two sets of code, a device-independent application and a device-specific player. Second, the patents disclose an authoring tool that allows for integration of web services into the application and player.

B. The accused products Two GoDaddy products are at issue in this case. WSB is a browser-based website creator, designed to allow a user with little or no website design experience to quickly create and publish a website. MWP, in contrast, targets more advanced users. It comprises a set of custom functionalities that GoDaddy has added to WordPress, an open-source (i.e. free) platform for creating websites. Both WSB and MWP allow for incorporation of features into a user's website, such as YouTube videos or embedded Twitter feeds. GoDaddy provides several free themes for use in designing a website, but users can also buy third-party themes for use with the MWP platform. C. Claim construction Two orders have previously been issued in this case construing certain disputed claim terms. Express Mobile, Inc. v. GoDaddy.com, LLC, No. 19-1937-RGA, 2021 WL 2209868 (D. Del. Jun. 1, 2021), and Express Mobile, Inc. v. GoDaddy.com, LLC, No. 19-1937-MFK, Mem. Op. and Order (dkt. no. 261) (D. Del. Aug. 8, 2022). The claim

terms relevant to the issues decided at trial were construed as follows: registry "a database that is used for computing functionality" player "device-specific code which contains instructions of a device and which is separate from the Application" device-dependent code code that is specific to the operating system, programming language, or platform of a device

D. Evidence at trial As relevant to the contentions Express Mobile has made in its motions, the following witnesses testified during the trial, either live or via deposition: • Dr. Kevin Almeroth, Express Mobile's infringement expert • Peter Kent, GoDaddy's infringement expert • Steven Rempell, CEO of Express Mobile • Ken Brown, Inventor of the asserted patents • Franklin Jarrett, GoDaddy engineer • Aaron Silvas, GoDaddy engineer

On a high level, GoDaddy argued that Express Mobile made a bad bet when it filed its patent applications back in 2008, as the patents are directed to device-specific players that have since been rendered obsolete. GoDaddy argued that, by contrast, its WSB and MWP products operate not via players but on browsers and that they use programming language such as JavaScript that is completely device-independent, which GoDaddy argued is necessary in the ever-evolving technological space of smartphones. The asserted patents recite nineteen claim elements. Kent testified, and GoDaddy argued based on his testimony, that neither WSB nor MWP infringe the asserted patents because they do not include three of the nineteen required claim elements: (1) "player" code that receives web service output; (2) "registry"; or (3)

"symbolic names." Regarding the player limitation, Dr. Almeroth testified, and Express Mobile argued based on his testimony, that WSB and MWP include device-dependent JavaScript player code that branches and accounts for different browser platforms. Because the player is also required to "receive the output symbolic name and corresponding one or more output values and provide[] instructions for a display of the device to present an output value," JTX-001 at claim 1, and because GoDaddy's products are browser-based, Dr. Almeroth testified that WSP and MWP infringe because their JavaScript players contain browser detection code that work together with other code to receive inputs and display outputs.

GoDaddy, for its part, argued that JavaScript—the primary programming language used in WSP and MWP—can work on all browsers and is thus not device- dependent-code. This argument was based in part on Kent's testimony that a browser cannot constitute a platform under the Court's construction of the "player" claim term. GoDaddy also argued that Dr. Almeroth confirmed on cross examination that the only specific code segments in each of the files that Express Mobile contends received the web service outputs were not, in fact, device-dependent code. Regarding symbolic names, Dr. Almeroth testified, and Express Mobile argued based on his testimony, that WSB and MWP use a registry that stores symbolic names, and that those symbolic names are incorporated into HTML code that is sent from GoDaddy's servers to its customers' web browsers. It further argued that the symbolic names stored in the registry were used for evoking web components. By contrast, Kent testified, and GoDaddy argued based on his testimony, that to

be a symbolic name, the name must evoke one or more web components and must be stored in a registry—a claim term that the Court construed as "a database used for computing information." Thus, GoDaddy argued, because the existence of a registry is required for the symbolic name claim element to be infringed (and vice versa)—and because the accused symbolic name does not evoke one or more web components or is not stored in a database—then there is no infringement. Kent explained that what Dr. Almeroth pointed to as symbolic names were actually something called "div IDs," which are randomly generated and thus cannot be stored in a registry. Kent also explained that, to the extent symbolic names or registry exist in WSB or MWP at all, they are kept and stored by the external web services intended to be accessed—like YouTube—and

not by GoDaddy. Discussion A.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Montgomery Ward & Co. v. Duncan
311 U.S. 243 (Supreme Court, 1940)
Exergen Corp. v. Wal-Mart Stores, Inc.
575 F.3d 1312 (Federal Circuit, 2009)
Finisar Corp. v. DirecTV Group, Inc.
523 F.3d 1323 (Federal Circuit, 2008)
Harris Corporation v. Ericsson, Inc.
417 F.3d 1241 (Federal Circuit, 2005)
Leonard R. Kahn v. General Motors Corporation
135 F.3d 1472 (Federal Circuit, 1998)
Eplus, Inc. v. Lawson Software, Inc.
700 F.3d 509 (Federal Circuit, 2012)
Donlin v. Philips Lighting North America Corp.
581 F.3d 73 (Third Circuit, 2009)
Marra v. Philadelphia Housing Authority
497 F.3d 286 (Third Circuit, 2007)
Zarow-Smith v. New Jersey Transit Rail Operations, Inc.
953 F. Supp. 581 (D. New Jersey, 1997)
Garrison v. Mollers North America, Inc.
820 F. Supp. 814 (D. Delaware, 1993)
Genzyme Corp. v. ATRIUM MEDICAL CORP.
315 F. Supp. 2d 552 (D. Delaware, 2004)
Mobilemedia Ideas LLC v. Apple Inc.
780 F.3d 1159 (Federal Circuit, 2015)

Cite This Page — Counsel Stack

Bluebook (online)
Express Mobile, Inc. v. GoDaddy.com, LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/express-mobile-inc-v-godaddycom-llc-ded-2023.