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?