Bonum Certa Men Certa

Guest Post: Watch Out for “Patented API” Traps, by Jose X

The Trap in a Nutshell



A patented API is short-hand for saying that an API (a software interface) is defined to parallel a patent so that using the API to build applications creates patented material unavoidably.



This is a trap API. Use it, and infringe.

The story:

Q: Can I "work around" the patent? Q: Can I re-implement the API libraries so as not to have to redesign and recode all apps? Q: Can I map or translate the app automatically into something safe?

A: In general, no, you can't, if the trap is a good one.

This covers the trap in a nutshell.

[The disclaimer: I am not a lawyer, and I have never written a patent application. But.. I do know how software works, and I have developed more than just half a clue about how patents work (in the US).]

Further Basic Discussion



For those that want a little more explanation, we have this link.

..as well as a hypothetical "Tetris" Patent Trap example.

Visual Basic function



"Tetris" Patent Trap



Patent Tetris Patent CoolDraw API Tetris API CoolDraw

We have two patents and two API. One patent and one API are high-level (Tetris). The other patent and API are low-level (CoolDraw). The high-level patent and high-level API are designed together as a trap as mentioned above. Ditto for the low level ones.

Let's look at a few more details on the patents and on the APIs. Then, we'll cover the four main scenarios. Do note the interplay of high-level with low-level. When the levels are the same (and matching), we have stepped onto the trap.

-- Patent Tetris: patents any tetris like game.

-- Patent CoolDraw: patents a cool way to draw on the screen from computer memory.

-- API Tetris: a createTetris function produces a tetris game when you input things like block size, colors, number of rows, time, etc.

-- API CoolDraw: a doCoolDraw function uses a cool algorithm to move values onto the screen.

Case 1: -- Patent Tetris -- API Tetris.

In this scenario, if we use API Tetris within our app so that a tetris game is created, we violate Patent Tetris, guaranteed.

Case 2: -- Patent Tetris -- API CoolDraw.

In this scenario, if we use API CoolDraw within our app so that we draw to the screen, we do not violate Patent Tetris unless we write a lot more code so as to create our own tetris game. It would take many lines of code to violate Patent Tetris.

Case 3: -- Patent CoolDraw -- API Tetris.

In this scenario, if we use API Tetris within our app so that a tetris game is created, we may violate Patent CoolDraw ..or not. It depends on how API Tetris was implemented. Does createTetris write to the screen the way described by Patent CoolDraw?

Case 4: -- Patent CoolDraw -- API CoolDraw.

In this scenario, if we use API CoolDraw within our app so that we draw to the screen, we violate Patent CoolDraw, guaranteed.

Quick Analysis

Case 1 (and Case 4) patent and API are at the same level (and matching). This is a trap. To avoid infringement, you have to redesign and re-code the application using a different API.

Case 2 is the case when people consider "working around" the patent. It's an odd event. You have to write many lines of code in order to possibly be infringing. If you are, you then try to code around it, perhaps by building something a little different than tetris. [In general, avoid infringement by make sure some of the properties of the patent claim are not met.]

Case 3 is the case where if a violation were to exist in the API implementation, you can try to re-implement the libraries and this way avoid re-implementing each and every single app as would be required for Cases 1 and 4.

The reason Case 3 allows you to re-implement the libraries and avoid re-coding up every application is fundamentally because you can re-implement the API but keep fixed the same interfaces and specifications enshrined in the API contract and assumed by the applications. This is not possible in Case 1 and Case 4 because any re-implementation of the same specification, for these cases, will infringe in the same exact way as with the original implementation since it's the specification itself (not any implementation of any part of it) that parallels the patent.

The reason Case 2 does not result in automatic infringement as happens with Case 1 and Case 4 is that the API interface and patent requirements don't match. It's that simple. Case 2 is where the application could possibly end up violating if you code enough with that API or with another. The Case 2 patent is high-level while the API is low-level. Case 3 is different in that the patent is low-level while the API is high-level; thus, Case 3 contrasts with Case 2 because in Case 3 the potential violations would not happen within the application (as with Case 2) but rather within the library.

In short, Case 1 and Case 4 are the only cases (of the four) where any API usage, by definition, specifies that the application will acquire all the properties of the matching patent claim. These are the traps.

Random APIs will not shadow any given patent as occurred in Case 1 and in Case 4. Developers normally would not have to worry. They can expect a Case 2 or a Case 3, if anything. However, Case 1 and Case 4 can be designed on purpose when the patent author and API designer are the same entity. Why would this author create this trap for developers? Well...

-- The patent author is determined to file lawsuits as necessary (maybe via proxies) in order to slow down many and/or key competing applications (eg, FOSS applications).

“You can be given a patent license and even GPL code for the core API, but not for the patented API extensions.”If you are using an API designed by such a vendor (regardless of who implemented the libraries), beware. I see lots of redesigning and re-coding in your future, just to get back to the same point (on a per app basis). Remember that the patent might still be in the pipeline, have been sold to a proxy, or have been developed through a partnership under a different company or alias.

The above nutshell and sample analysis omit many details. There are many corner cases and things are not cut and dried. In a second article to follow (possibly), we will look closer into many details of the trap scenario.

Finally, there is a more insidious trap that exists. You can be given a patent license and even GPL code for the core API, but not for the patented API extensions. You may then find that you can create only simple applications safely (with that core API), even if you decide not to use the patented extension API but build your own. This is more insidious because the patent and copyright licenses given for the core API give the illusion of safety (a green light to proliferate), and is insidious and dangerous all the more so since you might purposely avoid the patented extensions. The trap happens if you use the "safe" core with any extension whatsoever (since the extended patented properties can be very general in nature). The details of this extended insidious trap may form the subject of a third article later on. It's also described further here. ⬆

Comments

Recent Techrights' Posts

Harassment by Proxy in America - Part II - Decades of Misusing the Human Rights Tribunal of Ontario (HRTO)
We had seen this for quite some time
An Alluring Fantasy of Charlatans and Frauds
Last week we said that Huang should probably be arrested, not sacked
 
Links 22/11/2026: "The Bubble is Bursting" and "The Anthropic Bubble"
Links for the day
Andy Explains the 'Ritual' of Buy Nothing Day
old article about Buy Nothing Day
A List of Nadella's Accomplishments at Microsoft
Two weeks ago (exactly 2 weeks) everyone believed that Jensen was an excellent CEO too
Richard Stallman Gives a Talk in Guayaquil Tomorrow
Richard Stallman (RMS) is giving many talks in Ecuador, then he'll give several talks in Mexico as well
A Week After Microsoft Outages Windows is Measured at Only ~60% in North American Desktops/Laptops
Microsoft gives 2 more weeks for 60,000 of its own workers to announce they're leaving
Techrights Was Never a Political Site, It Deals With Mostly Technical Topics
There are people who try to weaponise politics to accomplish bad things inside or against the community
Techrights '30 Years Ago'
Don't mock people for still offering HTTP (not HTTPS-only) as an option
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, November 21, 2026
IRC logs for Saturday, November 21, 2026
IBM Hiding Layoffs by Telling Staff to Leave
IBM isn't a serious employer anymore. It also hides layoffs by twisting them as "resignations".
Kyrgyzstan: GNU/Linux Rises Above 5%
statCounter sees GNU/Linux at about 6%
Intrigue and Interest in GNU/Linux is Growing
Those of us who grew up in the previous millennium are accustomed to GNU/Linux being "that geek platform" that sites ignore because "only 1%" and whatnot
Gemini Links 21/11/2026: Blue Wave, Wes Huff, Jujutsu, and Tape Cassette Storage
Links for the day
To Trump's Sponsors, Microsoft and IBM, the Trump Mandate to Stop Sponsoring Visa Holders Was Actually a Blessing (More "Silent Layoffs")
"This is an easy excuse"
Uganda: GNU/Linux Measured at About 6%
Clownflare and statCounter measures aren't far apart, the metrics are
Links 21/11/2026: "Google’s Embrace of Hey Hi (AI) Is Backfiring Spectacularly" and Proton Turns to Slop
Links for the day
Links 21/11/2026: Sites "Overwhelmed by Slop Bots" and "Former SEC Chairman Gary Gensler Says Slop Is "Already a Bubble," Set to Pop and Cause Economic Catastrophe"
Links for the day
Harassment by Proxy in America - Part I - Targeting Women in Other Continents
There's no masculinity more toxic than this
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, November 20, 2026
IRC logs for Friday, November 20, 2026
Belatedly, the Real Nvidia Scandal (Corruption, Fraud) Comes Under US SEC Investigation
It had to happen soon or later
Gemini Links 20/11/2026: Electronic Rejection, Spectrum (Formerly Charter) Blocks Safe Websites, and Surveillance Jungle/Eavesdropping 1998
Links for the day
Links 20/11/2026: Microsoft to Pay in Shares Instead of Money and Over 10% at Intel Alleged at be Laid Off Again
Links for the day
IBM Will Continue to Sell Away Its Assets to Pay Salaries While Reducing Salaries (Fewer Workers, More Contractors, Offshoring)
The incredible thing is that the people who shrink IBM and lie to the media give themselves pay increases and bonuses
NVIDIA Corp Lost Almost Half Its 'Value' in a Matter of Weeks
the company that 'architected' or orchestrated this circular financing bubble is in peril
KDE is Good for Everybody
If Plasma isn't for "beginners", then why does does Valve made it the sole default in SteamOS/Steam Deck and why is it still around after 30+ years without any major controversy?
US Office of Government Ethics: NVIDIA Insider Trading by the Dictator of the US, Stock Soon 50% Below Its Value in October
It's just a rigged market, taxpayers are forced to pay for it (to bail out 'shy' billionaires)
Microsoft Morale Low, Drives Workers Crazy
Only a total moron with no grasp of technology would believe the catch-all excuse
No, IBM Didn't Lay Off Just "Hundreds" in 2026
These companies are rapidly shrinking. They just know how to hide what's really going on.
Slopapers: The Issue of Slop 'Wallpapers' Flooding the Repository in KDE and More
it's just an excuse that calls fusion (without attribution or any mention of a licence) "training" or "hey hi" or "fair use" or "superintelligence"
Links 20/11/2026: "Anthropic IPO [Shows] the AI Bubble Finally Popping" and New Problems With Slop Copyright Infringement
Links for the day
Richard Stallman, Founder of the GNU Project and a Co-founder of the FSF, Still Working With the FSF to Abolish Microsoft's Restricted Boot
Jack M. Germain has just published a lengthy article about GNU Boot
GNU/Linux Has Gained a Lot in Western Europe
Eastern Europe is another matter
IBM "Efficiency" is Working One's Way to the Bottom of the Remuneration Scale While Hiding the Stealth Layoffs
People still leaving
Forbes Already Stopped Being a News Site. Now It's a Spam and Propaganda Platform for "Paying Partners" (Companies).
news from Forbes became very scarce
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, November 19, 2026
IRC logs for Thursday, November 19, 2026
It's All About Restricted Boot and Microsoft
Garrett is working with Microsoft staff towards Microsoft agenda
Intercontinental Brigading - Part XXXXXVII - UK Isn't Part of the US or Russia
We have plenty to cover in the coming years
Update on Pocock v. Software in the Public Interest, Inc. (26-1766)
Case reassigned
Calling Frauds "Frauds" is Not Illegal
We are still getting the same vibe; Americans do not understand free speech, even if their country has a First Amendment
Everything is "AI" Now
"More Open Than Open [...] I am constantly amazed at the flexibility of this single word.”
Microsoft Web Sites Paint Mass Layoffs as Opportunities for Those Impacted, Mass Layoffs Alleged to Follow in January (to 'Kill Off' Survivors)
Keeping Up Appearances
Microsoft Outages Accelerate Migrations to Free Software
More than one major outage lately
Richard Stallman's Talks Next Month (Tech de Ciudad de México)
Right now is a very good time to promote Software Freedom because of recent world events