Patents & Intellectual Property
Prior Art and IP Strategy for Developers
How to search prior art, when to patent vs. use trade secrets, and separate advice for solo developers and employees.
How to Search Prior Art
A prior art search helps you understand whether your invention is novel, and whether a patent application is likely to succeed. You can do a preliminary search yourself for free before involving a patent attorney.
Tools for Prior Art Search
Google Patents (patents.google.com)
- Search by keywords and CPC (Cooperative Patent Classification) codes
- Use the "Advanced Search" to filter by date, inventor, and assignee
- The CPC code for software patents typically falls under G06 (computing), G06F (electrical computers), and G06Q (data processing systems for administration)
USPTO Patent Full-Text Database (patft.uspto.gov)
- Direct access to all issued U.S. patents
- Boolean search syntax: "database" AND "caching" AND "prediction" (with quotation marks for exact phrases)
Google Scholar (scholar.google.com)
- Find academic papers that may constitute prior art
- Sort by date to find earliest publications
GitHub commit history
- For software, commit timestamps establish prior art for specific implementations
- Search GitHub and the Wayback Machine (archive.org) for early implementations of similar approaches
Five-Step Search Strategy
- Identify the 3-5 key technical concepts in your invention
- Search each concept individually, then in combination
- Find the closest existing patents and read their claims carefully (not just abstracts)
- For each close match, note when it was filed and what it covers
- Document your search and its results — this demonstrates good faith and may support non-obviousness arguments
Defensive Publication
If you want to prevent others from patenting something but don't want to file a patent yourself, consider defensive publication. Publishing a technical disclosure makes your invention prior art for everyone — no one (including you) can subsequently patent it.
Options for defensive publication:
- The Defensive Patent License (DPL)
- IP.com's Prior Art Database
- A detailed blog post or white paper with a clear timestamp
- An open-source release on GitHub
Cost: $0–$500. Speed: immediate.
IP Strategy Framework
The right IP strategy depends on your situation. Here's a decision framework:
When to File a Patent
- The innovation is a core competitive differentiator
- It is detectable from outside (competitors can reverse-engineer it)
- You have $15,000–$30,000 to invest
- You expect to license it or use it defensively in litigation
When to Use a Trade Secret
- The innovation is not detectable from outside (internal algorithms, training data, processes)
- You can maintain secrecy with reasonable measures
- You want protection that lasts longer than 20 years
- Cost is a significant constraint
When to Defensively Publish
- You want to prevent others from patenting the idea
- You want the concept to remain open and available to everyone
- You don't want the cost or maintenance of a patent
- You're building on an open-source foundation
Advice for Solo Developers
You are probably not the target market for patents. The cost ($15,000–$30,000+) and time (2–3 years) make patents practical only if:
- You have a genuinely novel technical innovation with competitive moat value
- You can raise or allocate the budget
- You intend to license or litigate
More practical for solo devs: Trade secrets (keep it secret, sign NDAs with everyone who sees it), defensive publication (block others from patenting), and open-source licensing (choose a license that fits your business model).
Advice for Employees at Companies
Your employment agreement almost certainly includes an IP assignment clause. Before doing any technical work that might be patentable:
- Read your employment agreement's IP assignment section
- Understand whether your side projects are covered (see the next lesson)
- Know your state's protections (California, Washington, Minnesota, and Illinois have employee-friendly IP laws)
- Document anything you built before your employment start date
If you invent something at work that your employer chooses not to patent, ask whether they will assign it to you or allow you to defensively publish it.
Example
// IP strategy decision tree
type IPContext = {
isDetectableFromOutside: boolean;
hasBudgetForPatent: boolean;
wantOpenCommunity: boolean;
isCoreDifferentiator: boolean;
canMaintainSecrecy: boolean;
};
function recommendIPStrategy(context: IPContext): {
primaryStrategy: string;
reasoning: string;
estimatedCost: string;
} {
if (context.wantOpenCommunity) {
return {
primaryStrategy: 'Open Source + Defensive Publication',
reasoning: 'Maximizes community adoption while preventing others from patenting the idea',
estimatedCost: '$0–$500',
};
}
if (context.isDetectableFromOutside && context.isCoreDifferentiator && context.hasBudgetForPatent) {
return {
primaryStrategy: 'Utility Patent',
reasoning: 'Detectable innovation that is core to competitive advantage — patent provides enforceable exclusivity',
estimatedCost: '$15,000–$30,000',
};
}
if (!context.isDetectableFromOutside && context.canMaintainSecrecy) {
return {
primaryStrategy: 'Trade Secret',
reasoning: 'Internal algorithm/process not visible to competitors — secrecy is sufficient and cheaper',
estimatedCost: '$0–$5,000 (legal documentation and NDA enforcement)',
};
}
return {
primaryStrategy: 'Defensive Publication',
reasoning: 'Prevent others from patenting without incurring patent costs',
estimatedCost: '$0–$500',
};
}
const soloDevContext: IPContext = {
isDetectableFromOutside: false,
hasBudgetForPatent: false,
wantOpenCommunity: false,
isCoreDifferentiator: true,
canMaintainSecrecy: true,
};
console.log(recommendIPStrategy(soloDevContext));
// { primaryStrategy: 'Trade Secret', ... }