So because you wouldn't OPT-IN to receive the ads, you think it's fair not to allow others to opt-in?
We believe that with a solid opt-in in place, users should be able to support the developer by receiving Airpush ads.
Our mistake was we gave full control to the developers to build custom opt-in and opt-out using our Permissions API, whereas going forward we will FORCE a standardized opt-in dialog box.
It's one per day per DEVICE.
As stated we are moving to 100% opt-in. As a result, you will be able to block Airpush ads if you detest them so much, while other users can elect to keep them to help support the developer.
Can't we agree that user choice is the best option here? Or would you only be happy if the entire concept was eradicated? The latter doesn't make sense to me.
All -- we respect your feedback and are responding.
We are releasing an emergency update which will make Airpush ads OPT-IN by the users. Users will be prompted upon install if they want to support the developer by allowing 1 ad/day in their tray.
With this change, as a user would you find Airpush as an acceptable monetization option for the developer? This makes it purely a user's choice.
Please note we have already offered a "Permissions API" which many developers are using to create their own opt-in and opt-out procedures, but we are now taking the additional step of FORCING it in our SDK.
The support rep has given you wrong informaton. We ask all of our developers to put a notice in the Details page of their app, which APNDroid clearly had posted for all users to see. We also provide an API for developers to build custom opt-in and opt-out for the push notification ads.
Some users give bad ratings to many types of ad units, including rich media ads and full page interstitials.
That doesn't mean a developer should avoid them.
We believe that with a solid opt-in in place, users should be able to support the developer by receiving Airpush ads.
Our mistake was we gave full control to the developers to build custom opt-in and opt-out using our Permissions API, whereas going forward we will FORCE a standardized opt-in dialog box.