| I can't speak for _petronius, but what makes this guy obviously different from me is: * he thinks that an icon which links to something on the web is an "app", whereas I think that an app is something which contains a significant amount of program logic. * he thinks that changing the configuration (like YT channel id) generates a whole new app. This is like claiming that, at your Unix command line, "grep foo" is a different app from "grep bar" because we changed the string that it looks for. * he thinks that going from an "app" with a hard-coded YT channel to one with a user-configurable channel is a big step in development, the "real app". * he thinks he can no longer write apps for Android, whereas it is obvious to me that you can put a .apk file up for download anywhere you want, and get paid by means other than Google Wallet. * he cannot see what he obviously did wrong: make a spammy app that only re-frames other people's content, and infringes on trademarks, etc. In response to the first takedown, I would have pulled all copies of this app immediately. Google only holds power over those swaths of people who surrendered some aspects of their lives to Google. |
The author openly admits that this was a small, throwaway app that he wrote as an experiment, which contributed to his indifference as apps got suspended. It doesn't have to be complex to qualify as an "app".
I'm sure the author understands he can still write code for Android, but as he stated in the article, he might as well not if he expects any exposure. Alternative app stores and sideloaded APKs are used by approximately no one.
I don't think it can really be said he's liable for any kind of infringement just by using the YT API to wrap content. The issue would be in using the company name to imply endorsement of his applications, but even that could be a stretch. Should he have broken down to the old Red Hat trick and said "a prominent North American YouTube channel TV"?
While I probably wouldn't have made the same decisions this guy did, tolerance and handling of these types of uncommon miscommunications are part of the responsibility a company assumes when it decides to hook into so many parts of its users' lives. With the indispensability of something like Google, they really should be more careful before they mess up someone's life with this kind of action. Not everything can be resolved with a static, generalized FAQ.
The whole thing could've been averted if Google had taken the effort to clarify what was happening and why directly, by real communication from a human that is obviously personalized, at any point in the process.