How do you all handle AD removal upgrades?

[poken1151]

Hi All,

I was curious how other devs handle ad-free upgrades and similar items in their apps. Specifically, dealing with ensuring ads no longer run after a user has made a purchase.

Right now I feel my implementation is kind of crude; basically checking each launch for what's purchased (that's fine) and then setting IsEnabled on everything ad related I can to false, and setting visibility to collapsed on all items.

Anyone else have a more, "best practice" way of handling this, or just want to share your opinion?

 

[DavstarApps]

I handle it in much the same way--I usually add and remove the ad control from the view when the license is or is not a trial version, rather than just collapsing it. It seems a little crude as well, but having the ad control declared in XAML does make it possible to hack it and remove it since the XAML files for WinRT apps are stored in the open in the install folder, so people with access to that folder (more of a problem on Windows 8 than the phone, but still relevant). Having the ad control accessed in code will usually make it crash if they try and remove it.

Also make sure you tie into the license changed event, so if someone purchases it while the app is running it will immediately remove the ads without requiring a restart.

 

[nosaj_j]

We handle it in a similar way. When the app launches we check the licences then flag the relevant setting to false. We then created a simple extension method to convert booleans into a visibility type. Then simply assign the result to the visibility property in your viewmodel. Doing is this way means that you only have to do the 'logic' once, whilst every page that has an adcontrol will be updated automatically, thanks to the notificationchanged property on your viewmodels.