Native Pixel Inc v. Wavemaker Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Native Pixel Inc. (Florida)
  • Defendant: WaveMaker, Inc. (Delaware)
  • Plaintiff's Counsel: Cherry Johnson Siegmund James PLLC
• Case Identification: 2:26-cv-00205, E.D. Tex., 03/16/2026
• Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because Defendant maintains its principal U.S. headquarters and a regular and established place of business in Plano, Texas, where it employs personnel and conducts operations related to the accused products.
• Core Dispute: Plaintiff alleges that Defendant's low-code application development platform infringes patents related to systems for automatically generating platform-native graphical user interface code from design inputs.
• Technical Context: The dispute is situated in the low-code/no-code software development sector, a market focused on tools that accelerate application creation by translating visual designs and high-level logic into production-ready code.
• Key Procedural History: The complaint describes the asserted patents as originating from foundational work beginning in 2016 to address inefficiencies in traditional, manual user interface development. No prior litigation or post-grant proceedings are mentioned.

Case Timeline

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

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

The Invention Explained

• Problem Addressed: The patent's background describes the traditional software development process as inefficiently segmented, requiring designers' graphical mockups to be manually and expensively re-implemented as platform-specific code by developers ʼ459 Patent, col. 1:36-45 This process creates compatibility issues and high costs, particularly when targeting multiple platforms ʼ459 Patent, col. 2:13-22
• The Patented Solution: The invention proposes an integrated system that automates the conversion of graphical design inputs into native source code ʼ459 Patent, abstract The system accepts a graphic file, parses its elements, and recursively compares this input against a library of code templates to find a "best fit" ʼ459 Patent, col. 5:8-14 It then modifies this selected template to match the specific sizing, colors, and layout of the input design, ultimately compiling native code for the target device ʼ459 Patent, col. 6:40-62
• Technical Importance: The technology aims to provide a "single integrated front design and back end development solution" that decouples user interface design from platform-specific implementation, thereby addressing the persistent challenge of maintaining multi-platform operability ʼ459 Patent, col. 2:23-25

Key Claims at a Glance

• The complaint asserts independent claim 6.
• Essential elements of claim 6 (a system) include:
  • A hardware processor.
  • A front-end development software tool with a user interface element.
  • A "translation layer" for associating the UI element's function with device-native computer code.
  • A "template" that converts data from the function into native code by "recursively selecting one or more templates for each portion in a tree data structure," modifying them, selecting feature-based templates, and updating them with the native code and GUI design elements.
• The complaint reserves the right to assert additional claims Compl. ¶66

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

The Invention Explained

• Problem Addressed: As a continuation of the application leading to the '459 Patent, the '335 Patent shares an identical specification and addresses the same problem of inefficient, manual, and platform-dependent UI code development ʼ335 Patent, col. 1:36-45 ʼ335 Patent, col. 2:13-22
• The Patented Solution: The patented solution is likewise a system for automating the translation of graphical designs into native code for a target computing device. It employs a process of parsing design inputs and using templates to generate the final, platform-specific source code ʼ335 Patent, abstract ʼ335 Patent, col. 4:1-16
• Technical Importance: The invention seeks to solve the "problem of creating software programs that are design-driven and maintain multi-platform operability" by providing an integrated solution ʼ335 Patent, col. 2:13-15

Key Claims at a Glance

• The complaint asserts independent claim 19.
• Essential elements of claim 19 (a system) include:
  • A computer processor.
  • A computer-readable medium containing a front-end development software tool with a UI element.
  • A "translation layer" associating the UI element's function with device-native code.
  • A "template" that converts data by "recursively selecting one or more templates for each portion in a tree data structure," modifying them, selecting feature-based templates, and updating them.
• The complaint reserves the right to assert additional claims Compl. ¶81

III. The Accused Instrumentality

Product Identification

• The accused instrumentalities are Defendant WaveMaker's low-code application development platform and associated tools, including but not limited to its Web Studio, React Native Studio, AutoCode, CoPilot, and its "Agentic App Generation Platform" Compl. ¶29 Compl. ¶50

Functionality and Market Context

• The complaint alleges that WaveMaker's platform abstracts user interface design elements into an "environment-independent format" and then automatically generates native, production-ready source code for multiple target platforms, such as Angular for web applications and React Native for mobile Compl. ¶25 Compl. ¶30
• A core accused feature is a "Two-Pass Coding System" announced for its "Agentic App Generation Platform" Compl. ¶28 This system allegedly first ingests Figma design files or natural-language prompts and generates a "tech-stack-agnostic application markup" (referred to as 'WaveMaker Markup Language' or 'WML'). In the second pass, a "deterministic code generation engine" converts this intermediate markup into production code Compl. ¶28
• The complaint positions the accused products as part of a "leading low-code development platform" used by over 200 large enterprise customers Compl. ¶22 Compl. ¶24

IV. Analysis of Infringement Allegations

The complaint references claim chart exhibits that were not provided with the filing Compl. ¶49 Compl. ¶66 Compl. ¶81 Therefore, the infringement allegations are summarized below in prose based on the complaint's narrative.

No probative visual evidence provided in complaint.

'459 Patent Infringement Allegations

The complaint alleges that WaveMaker's platform, and specifically its "Two-Pass" architecture, infringes claim 6 Compl. ¶66 The asserted infringement theory suggests that the WaveMaker platform functions as the claimed "front-end development software tool" Compl. ¶¶25-27 The first pass of its system-converting design inputs like Figma files into an intermediate "WML" format-is alleged to be the claimed "translation layer." The second pass-using a "deterministic code generation engine" to convert the WML into native code-is alleged to perform the function of the claimed "template" that recursively selects and modifies code structures to generate the final output Compl. ¶28

'335 Patent Infringement Allegations

The infringement theory against claim 19 of the '335 Patent is parallel to that for the '459 Patent, based on the same accused "Two-Pass" functionality Compl. ¶81 The complaint alleges that WaveMaker's system, which first abstracts designs into a platform-agnostic markup and then generates native code from that markup, meets the elements of the system claimed in claim 19 Compl. ¶28 Compl. ¶29

Identified Points of Contention

• Scope Questions: A primary dispute may concern whether WaveMaker's intermediate, "tech-stack-agnostic application markup" constitutes a "tree data structure" as contemplated by the claims. Further, the court may need to determine if the process of converting this markup into final code is equivalent to the claimed "recursively selecting one or more templates."
• Technical Questions: A key factual question is how WaveMaker's "deterministic code generation engine" actually operates. The analysis may focus on whether this engine performs a recursive, template-matching process as described in the patent specification, or if its technical mechanism for code generation is fundamentally different from that claimed.

V. Key Claim Terms for Construction

• The Term: "recursively selecting one or more templates for each portion in a tree data structure" (appearing in asserted claim 6 of the '459 Patent and claim 19 of the '335 Patent).
• Context and Importance: This phrase describes the core technical mechanism of the claimed invention. The outcome of the infringement analysis will likely depend on whether WaveMaker's accused "Two-Pass" architecture, which converts an intermediate markup language into final code, falls within the scope of this term. Practitioners may focus on this term because it is the central point of contact between the patent's claims and the accused system's alleged operation.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: Language in the specification describes a process where the "software algorithm recursively compares the input information regarding the desired graphical user interface with the relevant templates to choose the template that closest represents the features" ʼ459 Patent, col. 5:8-14 This could support a construction that covers any iterative process of matching input characteristics to a library of code-generating structures.
  • Evidence for a Narrower Interpretation: The specification also discusses parsing "separate elements," "different layers," or "separate zones" of a graphic file ʼ459 Patent, col. 5:46-52 This could support a narrower construction that ties the "recursive" process specifically to the hierarchical structure of a visual design file (like a Photoshop or Figma file), rather than a more abstract, intermediate markup language.

VI. Other Allegations

• Indirect Infringement: The complaint alleges induced infringement, stating that Defendant provides customers with "promotional materials, product manuals, brochures, videos, demonstrations, and website materials" that instruct them on how to use the accused products in an infringing manner Compl. ¶60 Compl. ¶75 It also pleads contributory infringement, alleging the platform is a material part of the claimed invention that is not a staple article of commerce Compl. ¶56 Compl. ¶71
• Willful Infringement: Willfulness is alleged based on Defendant's knowledge of the patents "since at least the date of this Complaint" Compl. ¶65 Compl. ¶80 This suggests the allegation is primarily based on potential post-suit continuation of infringing activities.

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

• A central issue will be one of claim scope: whether WaveMaker's process of converting a proprietary, "tech-stack-agnostic" markup language into final code constitutes the "recursively selecting" and modifying of "templates" from a "tree data structure" as required by the patents' claims. The definition of these terms will be critical.
• A key evidentiary question will concern the precise technical operation of WaveMaker's "deterministic code generation engine." The case may turn on evidence showing whether this engine performs a step-by-step, recursive template-matching process as described in the patent specification, or if it operates on a different technical principle that falls outside the claim scope.