Ever since the empty anonymous reviews has been launched, my add-on has been made available for mobile platforms when I have already marked it as not compatible with mobile and even removed it from the version currently available and the one pending review.
How on earth are we suppose to make sure that mobile users are not being served an add-on that has been already marked as not compatible for mobile platform? Is this broken? Are all add-ons suppose to receive negative reviews because the users installed through AMO add-ons that are not compatible with the users’ platforms?
I would like to know what else is missing for us, developers, to do to make sure that users in incompatible platforms are not being served the incompatible add-on through AMO incorrectly.
I tested your add-on listing page on our mobile site (you can do this with an Android device or the Responsive Design Mode in the Developer Tools), and I don’t see way to install it by going directly to its page, or find it using the search tool. It would be useful for us to get more details on how users are finding it and installing it so we can fix the problem.
The same user continues complaining about add-ons showing up on the android section when they are not marked as compatible with android:
Why are these addons in the android section when they clearly are not compatible and the developer hasn’t tested! Here is another add-on does not do anything on android, this is retarded.
Clearly something is not right on AMO for this to be happening and the add-ons are the ones paying with negative reviews that are completely unfair and only the result of something broken on AMO.
As for providing more details on how users are finding and installing, I think that’s asking a bit much from any developer with almost no way to reach out for such task. We don’t have this kind of acces on AMO to do this.
One complaining could be a fluke, two could be a coincidence, but three, four, five, etc? At that point it is not something that should keep going ignored.
It is very sad that developers themselves will be forced to start adding an automatic landing page just to warn mobile users that the add-on is not mobile compatible and that they shouldn’t have installed it had Mozilla fixed this problem once and for all.