Joy Foroughi
Executive Assistant
Can You Patent an App? What Founders Should Know Before Building
Some inventions implemented through an app may qualify for a U.S. patent, but an app idea alone does not. The invention must meet requirements for patent eligibility, usefulness, novelty, non-obviousness, and sufficient disclosure. If your app solves a technical problem in a new way, a patent may be possible. If it is a familiar business idea on a phone, it probably is not. You also do not need a finished app to file, but what you do before and during the build can decide whether you keep the option at all.
Some inventions implemented through an app may qualify for a U.S. patent, but an app idea alone does not. The invention must meet requirements for patent eligibility, usefulness, novelty, non-obviousness, and sufficient disclosure. If your app solves a technical problem in a new way, a patent may be possible. If it is a familiar business idea on a phone, it probably is not. You also do not need a finished app to file, but what you do before and during the build can decide whether you keep the option at all.
TL;DR
A bare idea cannot be patented. The USPTO's basic patent guide says a complete description of the actual subject matter is required.
Software claims can qualify when they improve how a computer or technology works, rather than just using a phone to carry out an abstract goal.
You can file before the app is built, but public launches, sales, and demos can count against you. Plan the timing before you ship.
Initial government filing, search, and examination fees for a utility application total $400 for qualifying micro entities, $730 for qualifying small entities filing electronically, and $2,000 at undiscounted rates, before other applicable charges.
Put invention assignment and confidentiality terms in writing with every founder, employee, and contractor before anyone writes code.
What the USPTO will and will not patent
A patent is not a lock on a concept. It is a right granted for a new machine, process, manufacture, or similar subject matter, and the application has to describe it fully. The USPTO is explicit that a mere idea or suggestion cannot be patented.
That has a practical meaning for founders. Consider three pitches:
"An app that connects dog owners with local walkers." This is a business idea. Many apps do it, and the concept alone is not an invention.
"A matching engine that ranks walkers using live location, past routes, and battery-aware background tracking so the app stays accurate without draining the phone." This starts to look like a technical solution with specific steps.
"A new method for compressing and syncing offline data between a phone and a server that cuts bandwidth use." This is a technical improvement, and it is the kind of thing that has a chance.
The further you move from what the app is for toward how it does something technically new, the closer you are to patent territory.
The eligibility test, in plain terms
The USPTO applies a two-part analysis to software, laid out in its manual of patent examining procedure. Your claim must fit a statutory category, and it must not be directed to an abstract idea, law of nature, or natural phenomenon unless the claim as a whole adds significantly more than that exception. The agency's own guidance on subject matter eligibility says a software claim can be eligible when it clears both hurdles.
Does it fit a category?
The categories are process, machine, manufacture, and composition of matter. Most app inventions are framed as a process (a series of technical steps) or as a system (a device running specific logic). This step is rarely where apps fail.
Is it just an abstract idea on a phone?
This is where most app patents get stuck. Organizing a payment, matching two people, or scheduling a service are familiar commercial ideas. Running them on a smartphone does not make them inventions.
The USPTO's summary of Federal Circuit decisions points the other way for a certain kind of claim. It treats software claims focused on non-abstract improvements to computer technology as patent-eligible. Claims that improve computer functionality are stronger candidates than claims that merely use a computer as a tool for an abstract goal.
A useful self-check: can you describe your invention without mentioning the business use? If the technical contribution still stands on its own (a faster sync method, a new way to process sensor data, a different way to manage memory), you have something to discuss with a patent professional. If the only thing that makes it special is who it serves or what market it targets, you likely do not.
Is it new and not obvious?
Eligibility is only the first gate. The USPTO guide states that patentability also requires utility, novelty, and non-obviousness. An invention can be refused when prior art makes the differences obvious, even if no single reference shows it exactly.
Examiners search U.S. patents, published applications, foreign patent documents, and other literature, as described in the USPTO's overview of applying for patents. Competitive research can help you understand existing products and market alternatives. A patent prior-art search examines technical disclosures relevant to patentability, including patents, published applications, and other publications. TouchZen’s product strategy work can support market research, while a patent professional can assess the legal significance of prior art.
Do you need to build the app before you file?
No. The USPTO does not require a commercially finished product before you file. The application must adequately describe the invention and enable a person skilled in the relevant field to make and use it without undue experimentation. Two paths are common:
Provisional application | Nonprovisional utility application | |
|---|---|---|
Needs a written description and necessary drawings | Yes | Yes |
Needs claims | No | Yes, at least one |
Needs an inventor oath or declaration | No | Yes |
Leads to a patent on its own | No | Yes, if it is examined and allowed |
Lifespan | Generally expires 12 months after filing | Examined, then granted or refused |
The details come from the USPTO's page on applying for patents and its rules on provisional applications. A provisional can set an early filing date, but it must be followed by a proper nonprovisional filing within 12 months if you want to pursue a patent.
For a founder, the timing point is simple. A provisional application can establish an earlier filing date for subject matter it adequately describes. It does not grant enforceable patent rights. To preserve that filing-date benefit, applicants generally must file a corresponding nonprovisional application claiming the benefit within 12 months.
The flip side is the description requirement. A thin, vague write-up does not help you. The application must adequately describe the invention and explain how a person skilled in the relevant field could make and use it without undue experimentation. That is easier when your product team has already worked through the architecture, which is one reason a proper discovery phase pays off before filing.
Launching, demoing, and selling can affect your rights
This is the part founders most often get wrong. The U.S. system looks at what was publicly available before your effective filing date. Earlier patents, publications, public use, sales, or other public availability can be prior art. There is a limited one-year exception for certain disclosures made by the inventor, a joint inventor, or someone who got the subject matter from them, as the USPTO guide explains.
In app terms, think about these moments:
A public beta. Anyone can download it and see how it works. Read our beta testing guide for how to run one, and decide on your filing plan first.
An App Store or Google Play release. Releasing your app publicly on the App Store or Google Play can make the invention publicly available. Submitting an app privately for review is a separate step from releasing it; plan both using our App Store submission guide.
Demo days, pitch decks, and blog posts. A public explanation of how the technical feature works is a disclosure.
Early paid pilots. A sale or offer for sale is one of the events the USPTO lists as possible prior art.
The one-year exception is narrow and applies only in the United States context described here. Do not build a plan around it. If a patent matters to your business, speak with a registered patent attorney or patent agent before the first public beta or sale, not after.
A patent also asks something of you: it requires a complete description of what you invented. Most U.S. nonprovisional utility applications are published about 18 months after the earliest filing date for which priority or benefit is claimed, subject to exceptions. Provisional applications are not routinely published on their own. If your advantage is something competitors cannot easily see from outside, such as server-side logic, think about that tradeoff with your counsel before deciding to file.
What it costs to patent an app
Start with the government fees, because those are published. Under the USPTO fee schedule last revised November 1, 2026, the initial government fees for a utility application, covering filing, search, and examination, are:
Entity status | Initial utility filing, search, and examination | Provisional filing |
|---|---|---|
Undiscounted | $2,000 | $325 |
Small entity, qualifying electronic filing | $730 | $130 |
Micro entity | $400 | $65 |
These totals include the basic filing fee, so do not add it again. The basic fee is $350 undiscounted, $140 at the standard small-entity rate, or $70 for qualifying small entities filing electronically and for micro entities. Small- and micro-entity discounts require eligibility for the claimed status; being a startup alone does not establish eligibility. Other applicable charges are excluded. An issue fee is also due after allowance and before grant, and the USPTO notes that fees can change, so check the current schedule before you budget.
These numbers are the floor, not the total. They do not include a patent attorney or agent to draft the specification and claims, any drawings, or the back-and-forth with an examiner. Quotes vary widely by the complexity of the invention and the professional, so get written estimates from more than one before committing. A utility patent generally lasts 20 years from the relevant U.S. filing date, subject to maintenance fees.
Also keep in mind what you are buying. A patent gives you the right to exclude others from making, using, selling, or importing the claimed invention in the United States. It does not by itself give you freedom to practice your own invention, which may still depend on other people's patent rights and other laws.
Who owns the patent: founders, employees, and contractors
Ownership problems surface at the worst time, usually during fundraising or an acquisition. Three rules are worth knowing.
First, inventorship is about people, not companies. The USPTO's consolidated patent rules identify the inventor or joint inventors as the individuals who invented the claimed subject matter, even when the company is meant to own the patent.
Second, ownership is a matter of agreements. The USPTO states that a patent may be jointly owned, and that without an agreement to the contrary, each joint owner may exploit the invention and license or sell their interest without accounting to the others. A departing co-founder or outside developer who contributed to the claimed invention may retain ownership rights if those rights have not been assigned to the company. Writing code alone does not automatically establish inventorship.
Third, the paper needs to exist before the work does. Every founder, employee, and contractor who might contribute to the invention should sign a written invention-assignment agreement and confidentiality terms, and the company should record the assignments with the USPTO. A startup attorney can draft these in a short engagement, and it is much cheaper than untangling the question later.
The same logic applies to your development partner. Your contract should say who owns the code, designs, and any inventions that come out of the project. We cover the clauses to look for in our founder's checklist for IP in app development contracts.
Our perspective
We build apps for founders every week, and the patent question usually arrives at the wrong moment: right after a kickoff call, when someone wonders whether a competitor could copy the product. Our honest view is that the first thing to protect is the thing you can control, which is clarity about what you are building and who owns it.
That is why we work the way we do. Senior developers and designers talk directly with you from the first conversation. When the person designing your architecture is the same person explaining it to you, the technical choices that might be worth protecting get identified early, documented, and handed to your attorney in a form they can use. Nothing gets lost between a sales call and a junior team.
We encourage founders to validate demand while planning patent timing early. If patent protection may matter, discuss public demos, launches, and commercial pilots with a patent professional before proceeding. A patent describes a solution, and a solution only matters if the problem is real. Market research, competitive analysis, and an MVP definition help clarify your product’s commercial differentiation. A patent professional can separately assess whether the technical invention meets legal patentability requirements. The result is a product that is built for traction first, with a clear record of what is yours.
Bring your attorney in early, bring us in early, and let both conversations inform each other.
A pre-build checklist for founders
Use this order. It keeps your options open without slowing the build.
Write down the technical contribution. Describe how your app does something, not what it is for. If you cannot, treat patents as unlikely and focus on speed and brand.
Sign the paperwork. Invention assignment, confidentiality, and clear IP terms in your development contract, before work starts.
Talk to a registered patent attorney or agent. Bring your written technical description and your launch timeline, and ask about a provisional filing before any public beta, demo, or sale.
Control disclosure. Decide who sees what, and when, until your filing strategy is settled.
Search what exists. Review existing apps, published patents, and public product pages. The USPTO's description of examination shows that this is exactly what an examiner will do.
Validate the market. Validate demand within the disclosure and filing strategy agreed with your patent professional, keeping validation private where needed. A patent on an app nobody wants is a sunk cost. Our guides on validating your app idea and deciding in 30 days cover how.
Keep records. Save design documents, architecture diagrams, and dated notes as you build. They make the later description faster and more accurate.
Plan your scope. A tight MVP is easier to describe and easier to ship. Our one-week tradeoff rule for scope creep helps keep the build focused.
Pro Tip: Treat the filing decision as a product milestone with its own date, not an afterthought. Put "counsel consulted" on the roadmap ahead of the first public release.
Build the app with the right team behind it
Whether or not a patent is in your future, the product has to be built well, documented clearly, and launched on a plan. TouchZen has launched more than 75 apps across industries, and every engagement is handled directly by senior developers and designers. We support you from strategy and design through engineering, launch, and ongoing support.
If you are still shaping the concept, start with MVP development for startups. If you are ready to design and build, see our mobile app development service.
Tell us what you are building and where you are in the process, and we will help you map the path from idea to launch. Talk to the TouchZen team.
FAQ
Can you patent an app idea?
No. The USPTO states that a mere idea or suggestion cannot be patented, and that a complete description of the actual subject matter is required. What you can protect is a specific, new technical invention that your app implements, if it also meets the eligibility, novelty, and non-obviousness requirements.
How much does it cost to get an app patent?
Under the USPTO schedule last revised November 1, 2026, initial utility filing, search, and examination fees total $2,000 undiscounted, $730 for qualifying small entities filing electronically, or $400 for qualifying micro entities. Provisional filing fees are $325, $130, or $65, respectively. These are initial government fees, not the total cost of obtaining a patent. Attorney or agent fees, drawings, and examination responses come on top, and fees can change, so check the current schedule.
Do I need a working app before I apply?
No. A finished commercial product is not required, but the application must adequately describe the invention and enable a person skilled in the relevant field to make and use it without undue experimentation. A provisional application does not grant enforceable patent rights and expires after 12 months. A corresponding nonprovisional application generally must be filed within that period and properly claim the provisional’s benefit to retain its earlier filing date for adequately disclosed subject matter.
Does launching my app first hurt my chances?
It can. Public availability, public use, and sales before your effective filing date can be prior art. A limited one-year exception exists for certain disclosures by the inventor, but it is narrow, so speak with a patent attorney or agent before your beta, demo, or launch.
Who owns the patent if a contractor helped build the app?
The inventors named on the application are the people who contributed to the claimed invention, and ownership depends on your written agreements. Under U.S. law, absent an agreement to the contrary, joint owners can each exploit the invention without accounting to the others. A contractor is not automatically an inventor or joint owner simply because they wrote code. Get signed invention-assignment terms from every contributor before work begins.
