Someone Cloned Your App? How to Prove It

Resumo

Pixel shares a practical guide to investigating lookalike apps and distinguishing copied code or assets from a similar idea. It explains how to archive listings, compare bundles and unique markers, and contact hosts or app stores—while noting that a public-listing search is not proof and the guide is not legal advice.

DEV Community

Someone Cloned My App: How to Prove It and What to Do

Decide whether the clone used your code and assets, or just a similar idea. Archive the pages, save the bundle or binary, and record the URLs and dates before the listing changes. Compare unique strings, file structure, assets and any marker you planted against your own release. Then send a 512(c) copyright notice to the host, and use the official App Store dispute form if the copy is listed there. https://fortifie.xyz/cracked is a free search of public listings for your app, not proof. This guide is for the Mac or JavaScript developer who found a lookalike: a re-skinned copy, an AI-rebuilt web app, or your JavaScript bundle running on another domain. This is not legal advice. Talk to a lawyer if needed. Copied code or copied idea? Copyright can cover the way you expressed the app: source and bundled code, comments, text, images, icons, audio and other assets you created. It does not cover the idea of the app, a feature list, or a workflow someone else implemented with their own code and art. The US Copyright Office states this limit in Circular 1: Copyright Basics: copyright protects expression, not ideas, procedures or methods. Look at what they shipped. Your JavaScript bundle, unique functions, comments or error strings on their domain or in a GitHub repo is a code issue. Your icons, screenshots, marketing text or help files reused in their listing is an assets issue. An app that works like yours but was written from scratch, with different code and art, is usually a competition issue. Host and store complaint forms are not built for that case. An AI-rebuilt copy sits in one of those buckets too. If a model rewrote the UI and features without taking your files, you may have a lookalike with no copied code. If the published result still contains your bundle, comments, assets or a planted marker, treat it as copied expression and prove that overlap. A trademark, if you have one, covers your name, logo or other branding that identifies you, not your features. Talk to a lawyer about whether your facts support a copyright notice, a trademark claim, both, or neither. Capture proof before anything changes Listings, repos and store pages get edited or disappear. Capture what you see, then compare. If you do not have a URL yet, search here: Google: your app name plus "clone", "copy", "cracked" or "free download", and quote the name if it is generic. GitHub: the app name, a distinctive error string, a unique function or CSS class, or a comment you wrote. Other domains: a unique chunk filename, source-map path, or string from your bundle. The Mac App Store: search for your name and close spellings. https://fortifie.xyz/cracked is a free search of public listings for your app, not proof. It will not cover every host, and a name hit is not a confirmed copy. Once you have a listing, save it in a folder you can hand to a host, a store or a lawyer: Write down the exact URL, the date and time you found it, and the host or store name. Take full-page screenshots of the listing and any screens you can reach without signing in to a production account. Save a copy of the page and its assets. For a web app, download the HTML and the JavaScript, CSS and image files it loads, including .map files if they are still exposed. For a Mac app, do not download anything from a crack, warez or torrent listing; record that listing by URL and screenshot only. If the copy is offered as an ordinary download on the copier's own site or store page, save the archive to an isolated folder and do not launch the .app. Hash the saved files and keep the output next to them: shasum -a 256 path/to/saved-file
Keep your own originals in the same record: the release archive, git history, design files and store text, with dates. You can also submit the URL to a public web archive, such as the Internet Archive's Save Page Now. Do not depend on the live listing staying up. Your local copies and hashes are the record you control. If the copy is a Mac binary that might be y...
Someone Cloned Your App? How to Prove It
Powered by Readybot.io

As últimas novidades de Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …