I have some eye complications like dry eyes and due to this my doctor advised me cut down use of smartphone as much as I can. My first thought was to just get a feature phone and dump smartphone altogether. But there are few things about smartphone that I can not really give up now.
1. Maps - maps come in very handy at times when you are stuck in some unknown area and want to find way home.
2. Browser - to be able to check anything on the web is also very important to me.
3. Access to online storage and email.
Basically I gave up all social media, all smartphone gaming and other unwanted apps and use smartphone for basic internet access device. I have cut down my smartphone usage from 3 hours a day to about half an hour a day.
I'm hoping the author is way ahead of us. If he were smart, the game should be approved in iTunes and uploaded to Google Play, just ready for him to click "Publish" the moment this web version picks up some traffic.
Otherwise, Google Play will have a clone by the weekend if not sooner, and iTunes, maybe a week or two.
Somebody will definitely do it, on a throwaway dev account, but the original developer will only need to file a complaint and that account will almost certainly get banned for such blatant copyright infringement.
Well if the copier is intelligent enough it would easy and not time consuming at all to change the code in ways that would prevent such infringement laws to step in.
Fair enough, but look at all the duplicates out there for that piano keys game or...pretty much everything.
My question was supposed to geared more towards functionality. What advantage do you have making something in html5 when it's easily stolen. How do you prove it was yours first? I believe I read a blog post on HN about a guy who was cloned like this before he made it into the play store and google banned him instead of the copycat.
I think google cache can show that you created the website with the game first, then create a text file or something on the server that the support could access to show that you actually operate the site. If the other developer that has stolen the code can't provide a proof then it's fairly easy for the support to decide. The problem is of course that you need sane support for this to work.
One day I saw my son watching Khan Academy videos on YouTube and I wondered if I could make the experience easier for kids. [...] Wouldn’t it be cool if the could just click an app and instantly watch? So this was the initial inspiration and I wrote a simple YouTube client app using the latest YouTube APIs to watch Khan Academy videos. [...] The good thing about this app idea is that I can take any YouTube channel id, plug it into and now I’ve got another new app. So, one day I posted 10 apps to the play store with a few of my favorite YouTube channels and the Khan Academy channel and it was kind of exciting. [...] A few weeks went by and I got an email stating one of my apps had been suspended. [...] The suspension email stated that I was trying to impersonate another company, and that this was forbidden. [...] After a few more weeks another app was suspended. And again I thought: “OK, 2 down 8 more to go, that’s cool.” I was planning on taking all these apps down in a few weeks anyway. Another few weeks go by and a third app was suspended and also my entire Google play account was terminated for life.
3 apps suspensions and you're banned for life. Different rules apply for different violations, for copying someone's else code I think they would ban for life.
Google plays by their own rules and likely suspends only if someone files a DCMA claim or receives multiple reports from users. It's likely an automated system if it's from users. Getting your app. reinstated is unheard of, even if you weren't in the wrong. You will have to provide undeniable evidence to have any chance at re-instatement. The three strikes and-you're-out is not a hard-and-fast rule.
