I've been building an LLM-based web app for automated user-generated-content moderation. It's still around the MVP stage, but it's functional, has stronger security and moderation capabilities than the alternatives I've seen, and ranks well in search for several relevant terms.
Recently, I found another app being promoted as doing something similar. It appears to be a hastily assembled copy that only checks a few swear words with inline JavaScript and misses obvious cases. Its security scan results are also much worse than mine.
I'm not especially worried about competition, but I'm wondering whether there are risks I haven't considered. Could the other developer somehow claim that I copied them, especially if they tried to file something first? Should I document my work or take any other precautions? They didn't copy my code or branding, and they appear to have followed publicly available instructions from my blog. I'm mainly interested in protecting my work and establishing when I created it.
4 Answers
If they haven’t copied your code, branding, content, or other protected intellectual property, there may not be much you can do. General ideas and product concepts usually aren’t exclusive. The practical response is to keep improving the product and make its quality and reliability clear to potential customers.
Save evidence of your work now: dated screenshots, source-control history, deployment records, design notes, published articles, and archived versions of important pages. That creates a clear timeline showing what you built and when. You may never need it, but preserving the evidence is inexpensive compared with trying to reconstruct it later.
A weak competitor probably isn’t an immediate threat, especially if your app has better functionality, security, and search visibility. The bigger concern would be misleading branding, copied code or content, or false claims that confuse customers. If any of those appear, document them and consult an intellectual-property lawyer in your jurisdiction rather than assuming the first person to file paperwork automatically wins.
Being first with a working implementation and having dated public material can help establish prior development, but it doesn’t automatically give you ownership of the underlying idea. Signed change logs and carefully preserved publication records may help demonstrate provenance, while your main defense commercially is continuing to build a better product and reputation.
That makes sense. I can assemble the relevant records fairly quickly, and a few hours spent documenting the timeline seems worthwhile if it prevents a much larger problem later.