Native Pixel Inc v. Wixcom Ltd

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Native Pixel Inc. (Florida)
  • Defendant: Wix.com Ltd. (Israel)
  • Plaintiff's Counsel: Cherry Johnson Siegmund James PLLC
• Case Identification: 2:26-cv-00697, E.D. Tex., 08/14/2026
• Venue Allegations: Venue is asserted based on Defendant being a foreign company, which may be sued in any judicial district, and on Defendant's alleged commission of infringing acts, solicitation of business, and derivation of revenue from residents within the Eastern District of Texas.
• Core Dispute: Plaintiff alleges that Defendant's AI-powered application development platform, Base44, infringes three patents related to graphical user interface (GUI) generation and cross-platform delivery.
• Technical Context: The technology resides in the design-to-code and AI application-generation market, which involves systems that automate the creation of functional software from design artifacts or user descriptions.
• Key Procedural History: The asserted patents are part of a family with a shared prosecution history, including continuations and a continuation-in-part. The complaint alleges Defendant acquired the core accused technology, Base44, in June 2025. The complaint also references prosecution history materials to support the materiality of certain claim limitations.

Case Timeline

Date	Event
2016-11-16	Priority Date for '423 Patent
2017-02-10	Priority Date for '459 Patent
2017-02-10	Priority Date for '335 Patent
2019-06-25	'423 Patent Issued
2023-11-14	'459 Patent Issued
2024-10-15	'335 Patent Issued
2025-06-01	Wix acquires the Base44 platform (approximate date)
2026-01-01	Base44 launches mobile app-store packaging (approximate date)
2026-06-02	Base44 releases custom login pages feature
2026-08-14	Complaint Filed

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 10,331,423 - "Utilizing Cross Platform Streamable User Interfaces to Reduce Software Deployment Frequency Caused by User Interface Improvements", issued June 25, 2019

The Invention Explained

• Problem Addressed: The patent's background describes the inefficiency and "deployment friction" of updating user interfaces (UIs) for applications distributed through digital marketplaces (e.g., app stores) Compl. ¶50 Conventionally, every UI change requires rebuilding the application, resubmitting it for marketplace approval, and forcing users to download a new version, which can "impede user usage and damage brand positivity" '423 Patent, col. 2:1-9
• The Patented Solution: The invention decouples the UI from the main application binary. It proposes deploying a "container application" or "wrapper" to the marketplace that contains a "placeholder" for the UI but lacks the complete, specific instructions to draw it '423 Patent, col. 1:15-18 '423 Patent, col. 9:8-15 At runtime, this lightweight executable retrieves the current UI, stored server-side as an "environment independent view-controller object," and renders it for the user '423 Patent, abstract '423 Patent, col. 3:41-47 This allows developers to push UI updates dynamically without requiring users to reinstall the application Compl. ¶50
• Technical Importance: This architecture is designed to dramatically accelerate the development and deployment cycle for cross-platform applications, particularly in the mobile space, by enabling real-time UI updates.

Key Claims at a Glance

• The complaint asserts independent claim 12 Compl. ¶94
• The essential elements of claim 12, a computer program product claim, include:
  • Graphically designing a user interface (UI) archetype in an IDE project.
  • Generating an environment-independent view-controller object from the archetype.
  • Compiling source code into an executable "lacking sufficient drawing instructions to draw the user interface".
  • The executable comprises a reference to an object identifier and an instruction identifier.
  • Storing the UI object for retrieval during runtime.
  • Deploying the executable "within a digital marketplace".
  • During runtime, receiving the UI object by the executable and rendering the UI.
  • During runtime, "ignoring a user interface programming instruction embedded within the executable and rendering a different user interface from the UI object".
• The complaint does not explicitly reserve the right to assert other claims of the '423 Patent.

U.S. Patent No. 11,816,459 - "Graphical User Interface Programming System", issued November 14, 2023

The Invention Explained

• Problem Addressed: The patent identifies the high cost and complexity of traditional cross-platform software development Compl. ¶46 This process either requires maintaining entirely separate, hand-written codebases for each target platform (e.g., Swift for macOS, C# for Windows) or relying on middleware frameworks that introduce performance penalties like increased battery, CPU, and memory usage '459 Patent, col. 1:53-2:26 '459 Patent, col. 3:34-39
• The Patented Solution: The invention is a system that automates the conversion of GUI design elements into native code for various platforms '459 Patent, abstract It uses a "translation layer" and a template-based mechanism that operates on a hierarchical "tree data structure" representing the UI '459 Patent, col. 11:42-50 The system recursively selects templates for each part of the tree, modifies them to create output native source code, and separately handles "feature-based templates" for predetermined UI components (e.g., buttons, login forms) '459 Patent, col. 7:40-58 This process is designed to generate optimized, platform-native code without an inefficient runtime framework Compl. ¶54
• Technical Importance: This technology aims to bridge the gap between UI design and native code implementation, promising to reduce development time and cost while producing performant, platform-specific applications from a single design input.

Key Claims at a Glance

• The complaint asserts independent claim 17 Compl. ¶105
• The essential elements of claim 17, a system claim, include:
  • A hardware processor.
  • A front-end development software tool with a UI element associated with a function.
  • A translation layer associating the function with device native computer code for a first device.
  • A template that converts data into "computer-generated human readable created code" by a process including "recursively selecting one or more templates for each portion in a tree data structure".
  • This process includes updating feature-based templates with native source code and one or more GUI design elements "native to a second device".
  • The software tool processes input regarding a desired GUI, performs a similarity-based selection of a native-code template, and "assembles the code based upon the source tree structure".
• The complaint does not explicitly reserve the right to assert other claims of the '459 Patent.

U.S. Patent No. 12,118,335 - "GUI Generation System", issued October 15, 2024

• Technology Synopsis: As a continuation of the '459 Patent's application, the '335 Patent addresses the same technical problem of inefficient cross-platform development Compl. ¶41 Compl. ¶46 It claims a system comprising a front-end development software tool, a translation layer, and a template mechanism that converts UI design data into native source code by recursively selecting and modifying templates based on a tree data structure hierarchy '335 Patent, col. 13:1-14
• Asserted Claims: Independent claim 19 Compl. ¶117
• Accused Features: The complaint alleges that the Base44 AI App Builder's generation and project-maintenance architecture infringes by implementing the claimed front-end software tool, translation-layer functionality, and template mechanism Compl. ¶117 Compl. ¶118

III. The Accused Instrumentality

Product Identification

• The accused instrumentalities are Defendant's "Base44 AI App Builder" and its associated platform services, including generation, editing, project-maintenance, and hosting functions, as well as the "Base44 mobile app-store packaging capability and resulting WebView-wrapper applications" Compl. ¶3 Compl. ¶91

Functionality and Market Context

• The Base44 platform is described as an AI-powered tool that converts user inputs-such as natural language prompts, imported Figma designs, or screenshots-into functional applications Compl. ¶23
• It generates human-readable source code (React) organized in a project source tree, which users can inspect, edit, and export Compl. ¶24 The system uses reusable structures, including a "template marketplace" and pre-built, feature-keyed components for functions like user login Compl. ¶25
• A central accused feature is the mobile app packaging, which generates "a lightweight native wrapper around your web app that opens only your app's URL" and runs it "inside a secure web view" Compl. ¶28 Compl. ¶87 The complaint alleges that a critical capability of this feature is that design and content changes can be published to installed applications "without sending a new version to the Apple App Store or Google Play" Compl. ¶28
• The complaint positions these products within the "rapidly growing" market for design-to-code and AI application-generation solutions Compl. ¶20 No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

'423 Infringement Allegations

Claim Element (from Independent Claim 12)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
compile the source code into an executable lacking sufficient drawing instructions to draw the user interface within the target native runtime environment during runtime...	Base44's mobile packaging generates a "lightweight native wrapper" (an iOS IPA or Android AAB bundle) which allegedly lacks the specific instructions to render the full, server-hosted UI on its own.	¶87	col. 15:58-16:4
...deploy the executable lacking the user interface within a digital marketplace, wherein the marketplace provides access to the executable to a group of users authorized to use the marketplace;	Base44 generates store-ready application bundles and provides documentation instructing users to submit them to the Apple App Store and Google Play.	¶28; ¶95	col. 17:15-18:4
...during run-time of the executable, ignore a user interface programming instruction embedded within the executable and rendering a different user interface from the UI object by the executable.	The complaint alleges the Base44 wrapper contains initial app-shell UI instructions that are bypassed or superseded when the live, server-hosted UI is received and rendered, consistent with Base44's statement that updates appear without a new app version.	¶88	col. 18:11-18

'459 Infringement Allegations

Claim Element (from Independent Claim 17)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
a template that converts data from a first function into computer-generated human readable created code by recursively selecting one or more templates for each portion in a tree data structure...	Base44 allegedly processes hierarchical inputs (e.g., nested Figma designs) and applies a template-selection operation across portions of this hierarchy to generate human-readable React source code.	¶24; ¶78	col. 7:40-50
...updating the one or more feature-based templates with the native source code and one or more GUI design elements that is native to a second device...	Base44 is alleged to select templates for predetermined features (e.g., login pages), and its generator then updates these templates with generated native code and UI properties to create the final application code for the target device.	¶25; ¶81	col. 7:51-58
...the software tool...assembles the code based upon the source tree structure.	Base44 generates projects with a defined source tree (e.g., directories for pages, components, functions) and allegedly assembles the final application code according to this hierarchical organization.	¶24; ¶86	col. 16:32-36

Identified Points of Contention

• Scope Questions: A central dispute may concern the definition of "executable lacking sufficient drawing instructions" as recited in the '423 Patent. The court may need to determine if a WebView wrapper, which invokes a device's powerful system-level browser engine to render content, meets this limitation. For the '459 and '335 Patents, a key question will be the scope of "translation layer" and whether the functionality of a complex AI generation system can be said to be a "layer" that "associates" a function with code, as claimed.
• Technical Questions: The infringement theory for the '459 and '335 Patents relies on internal operations of the Base44 generator, such as "recursively selecting" templates "for each portion" of a tree Compl. ¶¶78-79 A technical question for the court will be whether the evidence, once produced in discovery, shows that Base44's AI-driven process performs these specific, structured operations, or if it operates in a fundamentally different, more holistic or probabilistic manner not contemplated by the claims.

V. Key Claim Terms for Construction

The Term: "executable lacking sufficient drawing instructions" (from '423 Patent, Claim 12)

• Context and Importance: This term is the lynchpin of the '423 Patent's infringement theory. Its construction will determine whether the accused "lightweight native wrapper" application, which relies on a device's WebView, can be considered to lack the claimed instructions.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The patent specification describes the goal of reducing deployment friction and enabling dynamic UI updates, suggesting the key inventive concept is the separation of the UI from the deployed binary, whatever its form '423 Patent, col. 2:1-9 Language describing a "placeholder functionality" could support an interpretation that any executable that cannot render the final UI on its own is "lacking" instructions '423 Patent, col. 1:15-17
  • Evidence for a Narrower Interpretation: The claim language requires the executable to lack instructions "to draw the user interface." A defendant might argue that a WebView wrapper, by invoking the full power of a system's browser engine, does not "lack" such instructions but rather delegates them. The specification also refers to creating a "wrapper library," which could imply a more specific structure than a generic WebView '423 Patent, col. 3:30-32

The Term: "translation layer" (from '459 Patent, Claim 17; '335 Patent, Claim 19)

• Context and Importance: Practitioners may focus on this term because its definition is crucial for mapping the claims onto an AI-driven generation platform. The complaint alleges this is not a single component but the broader "generator mappings/integration logic" Compl. ¶76
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The claims define the layer functionally as "associating the function... with a device native computer code" '459 Patent, cl. 17 This functional language may support a broader construction that encompasses the complex, multi-step process of an AI generator. The specification's goal is to replace manual coding and inefficient middleware, which could support reading the term to cover any automated system that achieves this end result '459 Patent, col. 2:12-26
  • Evidence for a Narrower Interpretation: The shared specification for the patents discusses a "User Interface Code Converter" '459 Patent, col. 3:50-51 This could be used to argue for a narrower definition of a more discrete, rule-based software component, in contrast to the alleged functionality of the Base44 AI.

VI. Other Allegations

Indirect Infringement

• The complaint alleges both induced and contributory infringement. Inducement is based on Defendant allegedly providing promotional materials, user manuals, and technical documentation that instruct customers on using the accused features, such as the mobile app packaging and AI builder, with the specific intent to cause infringement Compl. ¶96 Compl. ¶108 Compl. ¶120 Contributory infringement is based on allegations that Defendant supplies material components of the inventions-such as the Base44 generation platform and the wrapper executables-that are not staple articles of commerce and are especially made for infringing use Compl. ¶97 Compl. ¶109 Compl. ¶121

Willful Infringement

• Willfulness is alleged based on Defendant's knowledge of the Patents-in-Suit "since at least the date of the initial Complaint" Compl. ¶92 This asserts that any infringement occurring after the filing of the lawsuit is willful.

VII. Analyst's Conclusion: Key Questions for the Case

• A core issue will be one of architectural mapping: can the structured, step-by-step processes recited in the asserted claims (e.g., a discrete "translation layer", "recursively selecting" templates) be fairly mapped onto the complex, potentially probabilistic, and integrated operations of a modern AI-powered code generation platform like Base44?
• A second central question will be one of definitional scope: can an application described as a "lightweight native wrapper" that runs a web app "inside a secure web view" be considered an "executable lacking sufficient drawing instructions" under the '423 Patent, or does its reliance on the system's browser engine provide those instructions?
• A key evidentiary question will be one of operational proof: Plaintiff alleges specific internal software operations on "information and belief," such as the recursive selection and modification of templates Compl. ¶79 The case may turn on whether discovery yields technical evidence (e.g., source code, internal design documents, generator traces) that confirms the accused Base44 platform actually performs these granular steps as claimed, or whether it achieves a similar result through a fundamentally different technical process.