A developer ships an app. It gets 50,000 downloads in the first month. Users love the name. Then a cease-and-desist arrives from a company that registered that same name in Class 9 two years earlier. The app gets pulled from the store. The downloads, the reviews, the brand recognition, all gone. Not because the app was bad, but because nobody checked the trademark register before launch.
This happens more often than you'd think. Apple's App Store has 1.8M+ apps. Google Play has 3.5M+. Name collisions aren't a risk. They're a statistical certainty. And Class 9, the Nice classification that covers downloadable software, has over 847,000 active registrations at the USPTO alone. That's more than any other class.
If you're building a mobile app and you haven't filed to trademark the app name, you're exposed. Here's how the process works, what it costs, and where developers get it wrong.
Your App Store Listing Is Not a Trademark
Getting approved on the App Store or Google Play does not give you trademark rights. Apple and Google check whether a name is available on their platform. They do not check the federal trademark register. Two completely different systems.
This distinction matters because trademark rights in the United States come from one of two places: use in commerce (common law rights) or federal registration with the USPTO. Common law rights exist the moment you start selling under a name, but they're limited. They typically cover only the geographic area where you're actually doing business, and enforcing them requires proving you used the name first. That's expensive and uncertain.
Federal registration is different. It gives you nationwide priority from the date you file. It creates a legal presumption that you own the mark.
It lets you use the R symbol instead of just TM, which signals to competitors and platforms that your mark is on the register. And it gives you access to federal court if someone infringes.
Without registration, your enforcement options are thin. You can send a cease-and-desist letter, but it carries less weight. You can file a complaint with the app store, but platforms give priority to registered marks. You can sue, but common law cases are slower, costlier, and less predictable.
Your app store listing reserves a name on one platform. A trademark registration protects it everywhere.
What You Can Trademark: Name, Icon, Tagline
You can file a trademark for three types of assets related to your app.
Word mark (your app name). This is the most common filing for app developers. A word mark protects the name itself, regardless of font, color, or design. If you register "Relay" as a word mark, nobody else can use "Relay" (or something confusingly similar) for software in the same class.
Design mark (your app icon). You can trademark an app icon by registering it as a design mark. This protects the specific visual design. It's narrower than a word mark because it only covers that particular image, not the name. Most developers file the word mark first and add the design mark later if the icon becomes a recognizable brand asset.
Tagline or slogan. If your app has a tagline you use in marketing, that can be registered too. ("Connecting You to What Matters" or similar). It needs to be distinctive, not just descriptive of what the app does.
What you can't trademark: generic descriptions of your app's function. "Photo Editor" for a photo editing app is generic. "Fast Messenger" for a messaging app is descriptive. Neither will make it through examination.
Trademark law evaluates names on a distinctiveness spectrum. From weakest to strongest:
- Generic: "Weather App" for a weather app. Cannot be registered.
- Descriptive: "QuickScan" for a scanning app. Hard to register unless you prove years of consumer recognition.
- Suggestive: "Shazam" for a music identification app. Hints at magic/discovery without describing the function. Registrable.
- Arbitrary: "Apple" for technology. A real word in an unrelated context. Strong protection.
- Fanciful: "Spotify," "Zillow." Invented words. Strongest protection.
If you're still choosing a name, aim for suggestive or fanciful. They're easier to register, easier to defend, and easier to build a brand around. The same logic applies to SaaS products, where the naming challenges are nearly identical.
Which Nice Classes Mobile Apps Need
Nice classes are the international system for categorizing goods and services into 45 categories. When you file a trademark, you don't just register a name. You register a name for specific goods or services in specific classes. The class you choose determines who you're protected against.
For anyone looking to trademark a mobile app, two classes matter most:
Class 9 covers downloadable software. If your app is installed on a user's device, this is your primary class. It covers mobile applications, computer software, and downloadable electronic publications. With 847,000+ active registrations, it's the most crowded class at the USPTO.
Class 42 covers software as a service (SaaS). If your app connects to a cloud backend and the core functionality lives on your servers, you likely need Class 42 in addition to Class 9. Most modern apps have both a downloadable component and a cloud service. Filing in both classes covers the full product.
Some apps need additional classes depending on function:
- Class 35: If your app is primarily a marketplace or advertising platform (think product comparison, deal aggregation, or business directory apps)
- Class 38: If your app's core function is communication (messaging, video calling, social networking)
- Class 41: If your app delivers entertainment or educational content (streaming, courses, fitness coaching)
Multi-class filing costs more. A single-class application at the USPTO is $250 (TEAS Plus) to $350 (TEAS Standard). Each additional class adds that same fee. Filing in Class 9 and Class 42 together runs $500 to $700 in government fees alone, before attorney costs.
Typical Costs at Each Stage of App Trademark Registration
The decision comes down to risk. If your app is purely downloadable with no cloud component, Class 9 alone may be enough. If it has a backend, file both. The $250 to $350 for the second class is cheap insurance against a competitor registering your name in the class you skipped.
How to Trademark an App Name: 5 Steps from Search to Registration
The full process typically takes 8 to 12 months at the USPTO if nothing goes wrong. Here's each step.
Step 1: Search before you file. Check the USPTO's Trademark Electronic Search System (TESS) for existing registrations and pending applications. Search for exact matches and phonetic equivalents. "Relaay" and "Relay" sound the same and would likely create a conflict. Also search the app stores, domain registrars, and state trademark databases. A thorough search before filing saves you the $250 to $350 you'd lose on a rejected application, plus months of waiting.
Step 2: Choose your filing basis. The USPTO offers two paths:
- Section 1(a) (use in commerce): You're already using the name. Your app is live, users are downloading it, and you can prove it. You'll submit a "specimen" showing the mark in use, typically a screenshot of your app store listing.
- Section 1(b) (intent to use): You haven't launched yet, but you have a genuine intention to use the name. This lets you lock in your filing date and establish priority before launch. You'll need to submit a Statement of Use later, once the app is live, with an additional fee.
For developers still in development, Section 1(b) is often the right move. It lets you secure the name months before your app hits the store. The differences between US and EU filing are significant here: the EU doesn't require use evidence at filing, but the US does (or at least intent).
Step 3: Pick your filing option. TEAS Plus costs $250 per class and requires you to select your goods/services description from the USPTO's pre-approved ID Manual. TEAS Standard costs $350 per class and lets you write a custom description. For most apps, the ID Manual has suitable descriptions ("downloadable mobile application for [purpose]"), so TEAS Plus works fine.
Step 4: Submit and wait. After filing, your application enters the examination queue. A USPTO examining attorney reviews it for conflicts with existing marks, proper classification, and compliance with trademark law. If there's a problem, you'll get an office action (a letter explaining what needs to be fixed). You have six months to respond.
Step 5: Publication, opposition, and registration. If the examiner approves your application, it's published in the USPTO's Official Gazette. This starts a 30-day opposition period, a window where anyone who believes your mark would harm their existing rights can file a challenge. If nobody opposes (most applications aren't opposed), your mark proceeds to registration. For Section 1(b) filers, you'll need to submit your Statement of Use first, then registration issues.
The whole timeline:
- Filing to examination: 3 to 4 months
- Examination to publication: 1 to 2 months (if no office action)
- Opposition period: 30 days
- Publication to registration: 1 to 2 months (Section 1(a)) or longer (Section 1(b), depending on when you submit your Statement of Use)
Budget 8 to 12 months total. If you hit an office action or opposition, add more time.
5 Mistakes That Get App Trademark Applications Rejected
I've seen these patterns repeatedly. Each one is avoidable.
1. Filing too late. You launch, build momentum, then discover someone else filed first. In the US, the first to use generally wins. But if someone files an intent-to-use application before your launch, they can establish priority. The safest move: file a Section 1(b) application as soon as you've committed to the name, even if the app is months from launch.
2. Filing in the wrong class. A developer registers in Class 42 (SaaS) but forgets Class 9 (downloadable software). A competitor registers the same name in Class 9 for a mobile app. Now you have a conflict on the app stores, and your Class 42 registration doesn't help. Know what your app is (downloadable, cloud-based, or both) and file accordingly.
3. Choosing a name that can't be registered. Descriptive names feel safe because they tell users what the app does. "QuickPay" for a payment app. "FitTrack" for a fitness app. But descriptive names are the hardest to register. The USPTO will refuse them unless you can prove acquired distinctiveness, meaning years of use and significant consumer recognition. Pick a suggestive or fanciful name and save yourself the legal battle.
4. Ignoring international markets. Your app is available globally from day one. But your US trademark only protects you in the US. If your app gains traction in Europe, someone else can register your name at the EUIPO (European Union Intellectual Property Office) before you do. Many countries operate on a first-to-file basis, meaning whoever registers first wins, regardless of who used the name first. If you're planning international distribution, which most apps are by default, consider filing in key markets early.
5. Not monitoring after registration. Registration isn't the end. New apps launch daily, and some will use names confusingly similar to yours. Without active monitoring, you won't catch infringements until they've established a user base and become harder to stop. The same enforcement principles that apply to e-commerce sellers apply here: set up monitoring, and act quickly when you find conflicts.
How Apple and Google Handle Trademark Disputes
Both platforms have formal processes for trademark complaints, but they work differently than you might expect.
Apple accepts trademark complaints through its legal contact channels. If you own a registration, you can request removal of an infringing app. Apple reviews the complaint, contacts the other developer, and makes a determination. A federal registration significantly strengthens your case. Without one, you're relying on common law arguments, and Apple has little incentive to adjudicate those disputes for you.
Google Play offers a similar complaint process. You can report trademark violations through their support form. Google reviews the mark, the accused app, and the classes involved. Registered marks get faster, more decisive action. Unregistered claims often result in Google suggesting you "resolve this between yourselves," which means hiring a lawyer.
In both cases, a trademark registration is the difference between a strong complaint and a weak one. The platform needs a clear signal that you hold rights. A registration certificate is that signal. App store takedown requests citing trademark infringement have increased year-over-year, and both platforms have become more responsive to registered holders as a result.
There are limits to what app store complaints can do. A platform takedown removes one listing, but it doesn't stop the infringer from launching on another store, using the name on a website, or registering it themselves. For full enforcement, you need legal action outside the platform. The app store complaint is a useful first step, not a complete solution.
One more thing: both Apple and Google can and will take down your app if someone else has a stronger trademark claim. This cuts both ways. Registration protects you from being the one who gets pulled.
Before You Ship, Search
The developer in the opening story didn't have a trademark problem. They had a search problem. Ten minutes of checking before committing to a name would have revealed the conflict. The filing would have cost $250. Instead, they lost the name, the downloads, and months of work.
If you're building a mobile app, the sequence is simple: search, file, then ship. Not the other way around. The USPTO received over 612,000 applications in 2025. Class 9 has 847,000+ active registrations. Your name may already be taken.
Search for existing trademarks before filing. Signa provides API access to 147M+ records across 200+ offices at signa.so.
This article is educational and does not constitute legal advice. Consult a trademark attorney for guidance specific to your situation.