Paid to FREE w / IAP: Double Charge Prevention

Question

This is a conceptual workflow problem. I am converting an application with an existing user base from Paid to Free with in-app purchase (FWIAP) to remove ads. The problem I'm trying to avoid is that existing paid customers are updating the application, and now they suddenly see ads and insult / attack the “option” to pay again to remove ads that they never bought in the first place.

Fortunately, I have several breadcrumbs in the form of persistent data ( pData ) that will indicate whether the application has already been installed. So I decided to check out the new version for existing installations before deciding whether to continue showing ads.

One of the problems that I foresee is later updates, and then consideration of all those first-generation users who are now eligible for advertising, so I have to add another permanent flag ( pFlag ) to identify two groups of users, and then hope to recall even more recent updates (i.e. third generation, etc.) to check instead of pFlag instead of pData , since pData values ​​would have changed a long time ago.

Does this sound like a sound approach or is there another good known solution?

Answer 1

The problem with breadcrumbs is that users who upgrade or need to get a replacement device do not have recovery backups. When they re-download your application, there will be no breading.

Answer 2

I don’t think that someday you will be able to support cases when someone bought a paid version and installs it directly from the application store on a new device or device where the application was deleted.

We recently encountered this problem in the opposite direction. We have an FWIAP application that customers would like to purchase as part of a volume purchase program that does not apply to IAP. Thus, we created a paid version and sold it as a separate application, and it generates so many sales that the FWIAP version, basically doubling the revenues (for now).

I think the easiest approach is to just release a separate application. If you convert an existing application, the greatest risk is negative reviews, which can lower your star ratings and therefore download. Therefore, if you take this route, I will have such a generous customer support policy as possible - give anyone who claims to have bought a paid version of the code that allows them to unlock the FWIAP version.

But this may be a headache in the future, and from my limited experience you can make more money just by having both versions in the store.

Answer 3

The free-with-inapp-purchase paid workflow is supported; it is referred to as a paid-frame and is discussed in the 2013 WWDC video:

Using receipts to protect your digital sales https://developer.apple.com/videos/play/wwdc2013/308/