Defending your app from copies and clones
marco.org
marco.org
Marco rubs me the wrong way. Blanket statements like this are not meaningful.
What the post is saying is: there is nothing you can do. At the end of the day it doesn't matter who does it first, it matters who does it best. Do it best and you'll win.
Very clickbaity title. This could have been a tweet (and it was: https://twitter.com/sandofsky/status/966721199052013568)
The $20,000 part of patents (and additional legal fees) are a problem because we are clearly at the point economically where tons of people who need stronger protections will never have the resources to obtain those protections. You can’t do that when it’s impossible to sell anything for more than 99 cents.
Of course I go ahead and pay $50/year for ulysses or $20 for each Things 3 app, but my sister won't pay $3/m to iCloud on her filled up iPhone nor $5/m to Spotify or Apple Music to listen to music.
"Coincidentally, superior execution is also the most effective way to steal a good idea."
Right. Everyone should give their content to third party if they want to share it.
Does Mastadon float your boat, versus twitter?
If there's a patent, the force of law can be leveraged by the upstart to protect himself from such incursions, at least theoretically, and it requires expensive, tedious effort for the millionaire to circumvent the patent and/or defend himself against claims that he has infringed. Even if most inventors aren't going to pursue this course, the fact that the possibility exists is a deterrent.
Patents are not necessarily done well, but like many systems that have been co-opted by large corporate interests, they exist precisely to prevent such exploitation.
Software people must understand that software is not very hard or expensive to replicate. You don't get acquired because your software is good. You get acquired because you have a brand, an audience, a trademark, or a patent. There has to be some asset that the prospective acquirer cannot easily recreate by throwing 3-5 coders into a dark closet for a year or two (this costs around $1M / yr, much cheaper than any newsworthy acquisition).
So yeah, millionaires are likely to be very irritated that there's a patent that may force them to compensate the original innovator, or worse, buy their company entirely.
Marco is coming at from the perspective that everyone is a nerd, reads hacker news and knows the difference between "free beer" and whatever the other one is.
Most, nay, all software companies get shit patented. It's the difference between having a legal document protecting your ideas and, well, not.
The point is that you have no chance to defend yourself. Can an indy developer afford a legal defense of the scale required to "defeat" a major player? If they can will it even be worth their time and energy?
If you look at the world as if it was running on a tech tree in a video game, making closed source technology only forces people to retrace your footsteps(re-research the tech, if you will) or worse, find a better alternative (leaving you and your creation in the dust). By open-sourcing, you effectively stake a flag with your name on it in the tech tree and incentivize people to use your creation as a foundation for future techs. Sure, people will be free to use copies of your work at will, but they still have to give credit to you, and won't be trying to do things differently.
And that's not even mentioning that open-source stuff generally has a PR-boost compared to closed-source. If you make something closed-source, you will always have to worry about the appearance of an open-source competitor. I have seen closed-source stuff be completely eclipsed by open-source alternatives once the latter reached a critical level of quality. I mean think about it: Unreal Engine 4 is open source, would anyone start a closed-source project to compete against it? All the best minds will naturally ask you, 'Why not just work on UE4?' Yes you can fork it, but the public will always turn to the original of the fork unless your fork achieves something really different in a good way.
So in a way, open-source is the most asshole-way you can do things cause it shuts down any idea of a copy/similar alternative to your work.
Godot would be an example of an open source game engine.
https://www.engadget.com/amp/2012/11/09/silicon-knights-v-ep...
Simply attaching a big bad license to your code doesn't prevent 3rd world shovelware farms from copying your work and making tons of money from it for free.
Also, if everything were open-source, then nothing would get brownie points just for being open-source.
That's the thing about open-source though, it's a race to the bottom for market share. We saw it with React and Vue.
I also get that open-source is a maintenance liability with issue and requests, but I also see plenty of open-source software that do well "provided as-is".
As for closed-source competitors: game engines have always provided their source under proprietary licenses to people who paid enough, so the only real difference now is that you can get access to it (but with limited rights) without paying anything. But besides a few big names (Unity, Unreal and CryEngine/Lumberyard) there are quite a few closed-source competitors in use that don’t have generally available source code, although many of these are used only within a publishers development studios (idTech usually got open sourced after some time but until then the code wasn’t available to the public, Game Maker Studio, Frostbite etc)
On the style, the generalization "Only assholes get patents" turned me off quickly.
But on the content itself, there wasn't much in there that related to the title of the article "Defending your app from copies and clones": the author talks about copyrights, and trademarks (not patents, because apparently it's only for assholes), but explains how little use it is: am I supposed to be encouraged or discouraged to follow those paths?
Then the rest seems to be an exercise in despair, convincing you that there's nothing you can do anyways and you're screwed.
I ended the read a bit perplexed, as I wasn't able to squeeze any substantific marrow.
And try best not to compete directly with big players
I think this piece was intended as an eye opener, and a blunt one, because the world isn't going to soften its blows on you.
Everything in the article was related to the title, but I think your expectations were wrong. Instead of getting a list of things you can do to protect your app from copies, the author goes through the list of possible tools and explains why they don't really work.
However, this also means you can do the same thing to others without much fear so it really comes down to who can learn, adapt and create more quickly.
Not really - It's just that I don't feel like I learned much: I already knew about the challenges he mentions. Whether I like it or not is irrelevant. I was really interested in something "new" or "original" about it. That was my (perhaps misguided) expectation.
> Everything in the article was related to the title, but I think your expectations were wrong. Instead of getting a list of things you can do to protect your app from copies, the author goes through the list of possible tools and explains why they don't really work.
Yes, perhaps I shouldn't have set my expectations from the title "Defending your app from copies and clones", where I thought I was going to learn how to defend my app from copies and clones.
I think that's one reasonable interpretation of the title, although I can see how someone can argue that he never promised he'd give any solutions or original ideas in the title. It could indeed have meant "Defending your app from copies and clones: a lost cause". Those last 3 words I added do make it a better match for the content, don't you think?
Unfortunately what’s easiest for programmers is pretty easy to copy. For example, any ordinary file in an app bundle is dead simple to copy (and unfortunately the most straightforward APIs for using data from code will assume that files are plainly located in the bundle, which I always felt was a bit of a design oversight).
One fairly low-effort defense against copying is to use your program to reassemble valuable data from parts. For example, instead of having easily-stolen complete files in your bundle, store a variety of bits and pieces that only the program knows how to assemble correctly. You can even create a technically-corrupt/invalid binary file and then have your program restore the bits that you know you removed. Obviously this is an extra pain to do but if you really need to reduce the chance of losing to a competitor then it may be worth the trouble. (Note that this isn’t foolproof either, as clever people can still figure out what a program actually does; it’s just way better than doing nothing.)
Here’s the developer’s statement at the time:
http://asherv.com/threes/threemails/
The press and public opinion was mostly on the side of the Threes developer, perhaps because they were already fairly well respected in the indie game dev community; see for instance
https://www.wired.com/2014/05/threes-game-design
I mostly agree with Marco’s advice; but if you have your peers’ trust and approval, calling out your copycats seems like it might work in your favor (by bringing attention to your product for people who only know the copy). Or rather, let your hardcore fans call out the copy cats for you, and be brutally candid in your reaction - the devlog format of the Threes developers’ response was perfect for that.
Okay - Google patented their search. It's enabled them to stop the whole industry. Lets not go too far.
Interesting take, considering how Marco has called out both Pocket (formerly Read It Later) and Readability as having copied features that he claims to have created first.
"Weiner systematically copied almost every major Instapaper feature over the first few years of Instapaper’s existence", from https://marco.org/2013/02/21/the-first-read-later-service
and
"Over the next few months, they continued adding mostly Instapaper-like features to their service.", from https://marco.org/2011/11/16/readability
Perhaps his recent comments reflect how well his prior callouts were received?
EDIT: curious to know why this was downvoted. It wasn't meant as a dig at all—I was pointing out that Marco has experience with callouts and might have relevant expertise that many people lack. I would personally be very interested to hear his experience went dealing with those issues.
I used to like Marco, but after following him a while and noticing inconsistencies of principle like this, it got to me. (That, and when he said in a podcast that he didn't use SQL joins when building Tumblr because he doesn't like them. Trying to think about how he could have possibly accomplished that makes me shudder.) I can give him the benefit of the doubt that perhaps his perspectives have changed with age or experience, though.
All that said, I upvoted the OP too, because as much as I don't like the guy, he's not wrong here.
Fill in the blank, and the same lessons apply.
Any idea, project, business, app, website, article, podcast, TV show, media production, procedure, product, art, creation, etc are frequently copied and cloned. And he's right, ultimately nobody cares.
Sometimes a copy or clone is better than an original. Sometimes a copy or clone is much worse, but ends up successful because of positioning, luck, marketing, or savvy.
Perhaps it's better to think of the risk of being copied or cloned as part of the risk of business and creation. It just comes with the territory.
Of course, don't go and patent a mediocre interaction or technique, but definitely, pursue a patent if you have worked hard on researching and developing something that is key to your business and that could be used by a better established and wealthier competitor to take a market advantage.
I'd venture to suggest that most software patents are the obvious way of doing something. Even having read some attempts to justify them I see no merits in patents for XOR cursors, online auctions or shopping carts.
How are copyrights or trademarks ANY different? Together, they constitute essential tools in the knowledge/service economy. Demonizing patents but favoring the other two is ignorance on Marco's behalf - no one wants frivolous patents clogging the patent office, courts or legal departments of companies.
Apt advice would be to carefully research recent verdicts and legislation around patents, and only apply for ones that merit the designation (yes - this is very subjective).
These comments citing Apple and Google with their effective use of patents as some sort of counter argument seem to have missed the mark. Those guys are certainly able to afford $20k, and they can certainly afford to take on any adversary big enough to matter.
> Only assholes get patents. They can be a huge PR mistake, and they’re a fool’s errand: even if you get one ($20,000+ later), you can’t afford to use it against any adversary big enough to matter.
* the patent office seems to have a policy of grant-by-default
* the term is way too long for software patents
Grant 3-5 year patents and I think most of my objections would disappear.
I'm going to educate the public to avoid macro.org