[bredren]

I wonder if it is trivially hard to detect or not.

For example, if the app reviewer’s touch interaction with an app were recorded and the resulting screens diffed with the same pattern after publishing, there should be no changes.

This is a method used as part of some UI testing with selenium.

There could be apps this does not work for, such as when content changes or conversion type UI is shown.

But I imagine there is some amount of low hanging fruit here. And even that once a “scam” app like this one is reported, Apple should want to review past diffs to look for the example of the violation.

I also agree that for the price, this is what apple should be preventing on behalf honest developers

It is also worth noting that DMCA is embraced ITT whereas with Github’s response to DMCA recently it did not get the same treatment.

[Jenda_]

> For example, if the app reviewer’s touch interaction with an app were recorded and the resulting screens diffed with the same pattern after publishing, there should be no changes.

There are lots of valid reasons for apps to change based on outside events (location, time, online content). For example apps displaying weather forecast or current news.

[valuearb]

I think there is a solution and Apple should implement it. But even code we know how to write doesn’t appear overnight, doesn’t work perfectly, and doesn’t suffer from high levels of false positives.