I launched a Mac utility; now there are 5 clones on the App Store using my story
IP, DMCA, and Copying Boundaries
- Many commenters suggest DMCA takedowns for plagiarized text, images, and origin story; expectation is Apple will often remove blatant copies but not all.
- General consensus: copying the idea or simple functionality is fair game; copying marketing copy, assets, or decompiled code crosses a line.
- Some note legal recourse is impractical across borders and for low-revenue indie utilities.
What Can Be a Moat for a Simple Utility?
- Idea itself is not defensible; for a small Mac utility, suggested “moats” include:
- Speed of innovation and frequent updates.
- Better UX, native feel, and responsive support.
- Building a brand and community trust over time.
- Sheer stamina: keep maintaining while quick-buck clones decay.
- Others argue there may be no real moat for something that can be built in days; marketing and distribution dominate.
App Store, Distribution, and Clones
- Several argue that using the App Store means relying on Apple’s “moat”; curation is described as weak, random, or driven by volume/revenue rather than quality.
- Some criticize the 30% fee vs poor enforcement against obvious clones and spam.
- Suggestions include multi-cloning one’s own app with variations, direct distribution, and cautious use of Reddit and similar channels (avoid “I made $X in Y days” posts that attract copiers).
LLMs, Low Barriers, and Authenticity
- Multiple comments say LLMs have drastically lowered the bar to clone simple apps or marketing pages, intensifying an old problem.
- Broader unease emerges about AI-generated code, AI-written posts, and whether the thread itself is partly “vibe-coded,” raising questions about authenticity of both software and discussion.
- Some frame widespread cloning as a long-standing human behavior now amplified by new tools.