I've been building an LLM-based web app for automated user-generated-content moderation. It's still at the MVP stage, but it's a serious implementation rather than a quick prototype: it handles more than a few hard-coded swear words, has substantially better security practices, and is already ranking well for several relevant searches.
I recently found another app being promoted as doing something similar. After trying it, I found that its profanity filter was extremely basic—for example, it marked a disguised swear word as safe—and its security scan score was very poor. It appears to have been built by following instructions from my publicly available development blog, but it does not seem to use my code, branding, or other protected material.
I'm not especially worried about competition, but I'm wondering whether there's any hidden risk. Could the other developer somehow claim that I copied them, especially if they commercialize the idea first? Should I take practical steps now, or is it best to ignore the imitation and keep improving my own product?
3 Answers
A weak competitor is not necessarily a threat. If your app has better detection, security, documentation, and search visibility, those advantages matter more than being the first person to put up a similar landing page. Treat it as evidence that there may be demand, but don’t let a low-quality imitation distract you from improving the real product.
If they didn’t copy your source code, branding, or other protected assets, there may not be much you can do legally. General ideas and functionality are usually difficult to protect. The practical response is to keep building a better product, maintain your reputation, and make the differences in quality clear to potential customers.
Document your work now while the timeline is easy to prove. Save dated screenshots, deployment records, source-control history, design notes, published articles, and any original specifications. That won’t automatically give you ownership of the general idea, but it can help establish when your implementation and public claims existed if a dispute ever arises.
That makes sense. I can compile the relevant history and preserve it without much effort now, rather than trying to reconstruct it years later.