从带 IAP 的付费到免费:防止重复收费 [英] From Paid to FREE w/IAP: Preventing double-charging

问题描述

这是一个概念性的工作流程问题.我正在通过应用内购买 (FWIAP) 将具有现有用户群的应用从付费转换为免费以移除广告.我试图避免的问题是让现有的付费客户更新应用程序，现在突然看到广告并被侮辱/攻击选项"以再次付款以删除他们首先从未购买的广告.

This is a conceptual workflow problem. I'm converting an app with an existing user base from Paid to Free with an in-app purchase (FWIAP) to remove ads. The problem I'm trying to avoid is having the existing paid customers updating the app and now suddenly seeing ads and being insulted/assaulted with the "option" to pay again to remove the ads they never bought in the first place.

幸运的是，我确实有一些以持久数据 (pData) 形式存在的面包屑，用于指示应用程序是否已安装.所以我的想法是在决定是否继续展示广告之前让新版本检查现有安装.

Luckily, I do have some breadcrumbs in the form of persistent data (pData) that will indicate whether the app was already installed. So my thought is to have the new version check for existing installs before deciding whether to proceed with displaying the ads.

我预见的一个问题是稍后更新然后考虑所有这些第一代用户现在再次符合广告条件，因此我必须添加另一个持久标志 (pFlag) 来识别这两个用户组，然后希望记住以后的更新(即第三代等)以检查 pFlag 而不是 pData，作为 pData 值到那时早就改变了.

One problem I foresee is later updates then considering all those first-generation users as now eligible for ads again, so I'd have to then add another persistent flag (pFlag) to identify the two groups of users and then hope to remember for even later updates (i.e. third-gen., etc.) to check against the pFlag instead of the pData, as the pData values would have long changed by then.

这看起来是一个合理的方法还是有其他众所周知的解决方案?

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

推荐答案

面包屑方案的问题在于用户升级或必须更换设备，但没有备份可从中恢复.当他们重新下载您的应用时，将没有面包屑.

The problem with breadcrumb schemes is with users who upgrade, or have to get a replacement device, and don't have backups to restore from. When they re-download your app, there will be no breadcrumb.

这篇关于从带 IAP 的付费到免费:防止重复收费的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！