DCT

2:26-cv-00771

Native Pixel Inc v. Wavemaker Inc

Log In
Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 2:26-cv-00771, E.D. Tex., 08/28/2026
  • Venue Allegations: Venue is alleged to be proper based on Defendant maintaining its principal U.S. headquarters, a regular and established place of business, in Plano, Texas, within the Eastern District of Texas, and having committed acts of infringement in the District.
  • Core Dispute: Plaintiff alleges that Defendant's low-code and AI-powered application development platform infringes a patent related to a client-server architecture for streaming user interfaces to deployed native applications at runtime.
  • Technical Context: The technology addresses inefficiencies in software development by decoupling the user interface (UI) from the application's core logic, allowing for UI updates without recompiling and redeploying the entire application through digital marketplaces.
  • Key Procedural History: This action is related to a prior case between the same parties involving patents from the same family. The patent-in-suit, U.S. Patent No. 10,331,423, expired in June 2023 for non-payment of a maintenance fee but was subsequently reinstated by the USPTO in June 2026 upon a finding that the delay in payment was unintentional. The complaint seeks damages only from the date of reinstatement forward, a strategic choice that may be intended to preemptively address potential intervening rights defenses under 35 U.S.C. § 41(c)(2). The complaint also references the patent's prosecution history, noting the examiner's allowance distinguished the invention from prior art.

Case Timeline

Date Event
2016-11-16 '423 Patent Priority Date
2017-08-16 '423 Patent Application Filing Date
2019-06-25 '423 Patent Issue Date
2023-06-25 '423 Patent temporarily expired for non-payment of maintenance fee
2026-02-19 WaveMaker announced its "Two-Pass Coding System"
2026-03-16 Related case (2:26-cv-00205) filed by Plaintiff against Defendant
2026-04-21 WaveMaker and Accenture announced strategic intent to combine technologies
2026-06-04 USPTO reinstated '423 Patent
2026-08-28 Complaint Filing Date

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

  • Patent Identification: U.S. Patent No. 10,331,423 B1 ("Utilizing Cross Platform Streamable User Interfaces to Reduce Software Deployment Frequency Caused by User Interface Improvements"), issued June 25, 2019. Compl. ¶4

The Invention Explained

  • Problem Addressed: The patent's background describes the conventional software development process as inefficient and costly Compl. ¶21 '423 Patent, col. 1:46-48 The core technical problem is that user interfaces are typically compiled statically into an application's executable file, meaning any UI change, no matter how small, requires recompiling and redeploying the entire application, often through a lengthy app store approval process Compl. ¶22 '423 Patent, col. 5:58-65
  • The Patented Solution: The invention proposes a new software architecture to solve this problem by separating the UI from the application logic Compl. ¶24 UI characteristics (layout, controls) are abstracted into an environment-independent "view-controller object" stored on a server '423 Patent, abstract The application deployed to a user's device is compiled to deliberately lack these UI details, instead containing a "placeholder functionality" that is configured at runtime to fetch, process, and render the UI by streaming the UI object from the server '423 Patent, abstract '423 Patent, col. 9:17-24 This allows developers to update the UI on the server, and the changes are reflected in the user's application immediately without requiring an application update Compl. ¶27 '423 Patent, col. 5:65-6:5
  • Technical Importance: This server-driven UI architecture enables rapid iteration and dynamic content delivery, which was becoming increasingly critical for mobile and web applications that need to adapt quickly to user feedback and market changes Compl. ¶6

Key Claims at a Glance

  • The complaint asserts infringement of one or more claims of the '423 Patent, with specific narrative analysis provided for independent claims 1 (method), 10 (system), and 12 (computer program product) Compl. ¶51 Compl. ¶74
  • The essential elements of representative independent claim 12, a computer program product claim, include:
    • Graphically designing a UI "archetype" in an integrated development environment (IDE).
    • Generating an "environment independent view-controller object" from the archetype.
    • Compiling source code into an executable that is "lacking sufficient drawing instructions to draw the user interface," but which contains references to an object identifier and instruction identifiers.
    • Storing the UI object for retrieval during runtime.
    • Deploying the "executable lacking the user interface" within a digital marketplace.
    • During runtime, the executable receives and processes the UI object to draw the user interface.
    • During runtime, the executable ignores any embedded UI programming instruction in favor of "rendering a different user interface from the UI object."
  • The complaint notes that it reserves the right to assert other claims, including dependent claims that add further limitations Compl. ¶51

III. The Accused Instrumentality

Product Identification

  • The complaint identifies a suite of products and services collectively referred to as the "Accused Instrumentalities," centered on the WaveMaker low-code application development platform (the "WaveMaker Platform") Compl. ¶54 Compl. ¶55

Functionality and Market Context

  • The WaveMaker Platform is described as a low-code, AI-powered tool used by enterprise customers to build and deploy applications Compl. ¶54 The complaint alleges that the platform's architecture mirrors the patented invention. Key alleged functionalities include:
    • Abstraction: A visual studio is used to create designs that are translated into an "intermediate WaveMaker meta markup language (WML)," which is described as a "tech-stack-agnostic" and "universal meta model" Compl. ¶¶55-56
    • Two-Pass System: The platform allegedly uses a "Two-Pass Coding System." In the first pass, the WML is generated. In the second, a "deterministic transpiler converts generated WML into production Angular, React JS or React Native code" Compl. ¶59 Compl. ¶23
    • Runtime Dependency: Generated applications are not self-contained but are "bound to the WaveMaker runtime," which manages UI rendering, data binding, and other functions Compl. ¶57
    • Server-Side UI: UI configurations are allegedly "stored in the backend as a JSON file for the page," which are then "retrieved and processed at application startup" Compl. ¶57
    • Marketplace Deployment: The platform enables the creation of installable packages (APK/IPA) that can be listed on app stores, with allegations that UI artifacts can be packaged separately from the executable Compl. ¶58

IV. Analysis of Infringement Allegations

No probative visual evidence provided in complaint.

The complaint alleges that the WaveMaker Platform infringes the '423 Patent by practicing the claimed methods and embodying the claimed systems Compl. ¶74 The following table summarizes the infringement theory for representative claim 12, based on the narrative allegations in the complaint.

'423 Patent Infringement Allegations

Claim Element (from Independent Claim 12) Alleged Infringing Functionality Complaint Citation Patent Citation
...graphically design a user interface (UI) archetype associated with a software development project of an integrated development environment (IDE)... Defendant's platform provides a "visual, drag-and-drop design studio" for designing application UIs. ¶55 col. 2:45-51
...generate an environment independent view-controller object from the archetype... The platform generates a "tech-stack-agnostic application markup (WML)" that abstracts UI characteristics into an "environment-independent format." ¶59 col. 2:55-59
...compile the source code into an executable lacking sufficient drawing instructions to draw the user interface...wherein the executable comprises of a reference to the object identifier and...instruction identifier... The platform builds "target-native executables" where UI artifacts can be delivered separately and UI variables are stored in a backend JSON file, suggesting the executable lacks the full UI. The executable is "bound to the WaveMaker runtime," suggesting the presence of references. ¶57; ¶58 col. 2:60-64
...store within a computer readable storage medium the UI object for retrieval during runtime execution of the executable... The platform's documentation allegedly states that UI variable configuration "is automatically stored in the backend as a JSON file for the page," which is "retrieved and processed at application startup." ¶57 col. 2:65-68
...deploy the executable lacking the user interface within a digital marketplace... The platform builds and deploys "installable APK (Android) and IPA (iOS) packages" so that applications "can be listed on the app stores." ¶58 col. 18:1-4
...receive and process the stored UI object during runtime execution of the executable... The platform's runtime retrieves and processes the backend JSON file containing UI configuration "during page load or application startup." ¶57 col. 17:5-10
...draw the user interface...using the drawing instructions of the UI object... The "WaveMaker runtime" allegedly "manages: Page lifecycle...Two-way data binding between UI components and variables" and uses React as a "rendering framework" to display the UI defined by the retrieved data. ¶57 col. 17:11-14
...ignore a user interface programming instruction embedded within the executable and rendering a different user interface from the UI object by the executable. The architecture of retrieving UI definitions from a backend server at runtime implies that any default or compiled-in UI would be ignored in favor of the dynamically loaded UI. ¶26; ¶57 col. 18:14-18

Identified Points of Contention:

  • Scope Question: A central question may be whether WaveMaker's "WML" and runtime JSON data constitute a "view-controller object" within the meaning of the patent. The defense may argue that its architecture uses standard, non-infringing web or MVC paradigms, while the plaintiff will likely contend it is the specific, unconventional architecture claimed in the patent.
  • Technical Question: The allegation that the accused executable is "lacking sufficient drawing instructions" is a negative limitation that could be a point of dispute. The analysis may require a technical deep-dive into the structure of the compiled applications to determine if they are truly "lacking" instructions, or if they simply contain instructions that are overridden by the runtime-loaded data.
  • Technical Question: The complaint alleges that the WaveMaker runtime controls UI rendering Compl. ¶57 A key factual issue will be establishing that this runtime performs the specific sequence of steps recited in the claims, such as processing the UI object and using its "drawing instructions" to render the interface, as opposed to a more generic data-binding process.

V. Key Claim Terms for Construction

The complaint identifies several terms as material to the dispute Compl. ¶52 The construction of the following terms may be particularly central.

  • The Term: "placeholder functionality"
    • Context and Importance: This term defines the client-side component responsible for receiving and rendering the streamed UI. Its construction is critical to determining whether the "WaveMaker runtime" Compl. ¶57, which is coupled with the deployed application, meets this limitation. Practitioners may focus on this term because it appears to describe the "hook" in the client application that enables the entire server-driven UI system.
    • Evidence for a Broader Interpretation: The specification describes it broadly as "a framing mechanism for integrating layout instructions, arbitrary control elements..." '423 Patent, col. 9:17-20
    • Evidence for a Narrower Interpretation: The description of the placeholder being "dynamically replaced... by a streamable user interface" '423 Patent, col. 3:45-48 and the depiction of a distinct "UI Placeholder 154" in Figure 1 could support an argument that the claim requires a discrete, identifiable component, not just the general function of a runtime engine.
  • The Term: "view-controller object"
    • Context and Importance: This term defines the data structure that is abstracted from the application and streamed from the server. The infringement case hinges on whether WaveMaker's "WML" or backend JSON files fall within this definition.
    • Evidence for a Broader Interpretation: The patent abstract defines it as an object that "conforms to an environment independent format" and into which "one or more characteristic[s] of a user interface... can be abstracted." This suggests a functional definition.
    • Evidence for a Narrower Interpretation: The patent explicitly distinguishes its invention from traditional Model-View-Controller (MVC) patterns, stating it "leverages a decoupled approach to MVC" '423 Patent, col. 6:44-45 A defendant might argue this language limits the term to a specific, non-standard structure, and that their own architecture is conventional and therefore outside the claim scope.
  • The Term: "lacking sufficient drawing instructions"
    • Context and Importance: This is a negative limitation describing the state of the deployed executable. Its interpretation will determine the evidentiary burden for proving infringement.
    • Evidence for a Broader Interpretation: The language "lacking sufficient instructions" could be interpreted to mean that the executable is incapable of rendering the complete, final UI on its own, even if it contains some basic UI elements like a splash screen or error dialogs.
    • Evidence for a Narrower Interpretation: A defendant could argue that this requires the executable to be almost completely devoid of UI-related code, a high bar to prove for any modern application. The presence of any compiled-in UI rendering code, even if later ignored, might be argued to defeat this limitation under a narrow construction.

VI. Other Allegations

  • Indirect Infringement: The complaint alleges inducement by citing Defendant's documentation, tutorials, and marketing materials, which allegedly instruct customers to use the WaveMaker Platform in an infringing manner Compl. ¶76 It also alleges contributory infringement, asserting that Defendant supplies key components like its runtime engine and code generators, which are material to the invention and have no substantial non-infringing use in the accused architecture Compl. ¶79
  • Willful Infringement: Willfulness is alleged on two grounds. First, Defendant allegedly had knowledge of the patent family since March 2026 via a related lawsuit, and continued its conduct despite this awareness Compl. ¶88 Second, the filing of the present complaint allegedly constitutes notice, making any subsequent infringing activity willful Compl. ¶88

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

This case appears to be a sophisticated, technically-focused dispute over the architecture of a modern software development platform. The outcome may turn on a few central questions:

  1. A core issue will be one of definitional scope: Can the patent's key architectural terms, such as "view-controller object" and "placeholder functionality", be construed to read on the components of Defendant's platform, like its "WML" and runtime engine? This will likely be a heavily contested claim construction battle.
  2. A key evidentiary question will be one of structural proof: Can the plaintiff demonstrate that executables generated by the WaveMaker platform are structurally "lacking sufficient drawing instructions" as required by the claims? This question moves beyond marketing materials and may require forensic analysis of the accused compiled application code.
  3. A secondary issue involves the patent's procedural history: While the plaintiff has attempted to neutralize defenses related to the patent's temporary lapse and reinstatement by limiting its damages period, the court will still need to affirm that no intervening rights or other equitable defenses arise from the Defendant's conduct during the period the patent was expired.