3 ms·
> "The UI for recovering an in-app purchase is the same as the buying UI, which leads many users to mistakenly believe they are being double-charged." This mak
by chucknelson 14y ago
> "The UI for recovering an in-app purchase is the same as the buying UI, which leads many users to mistakenly believe they are being double-charged."
This makes sense for low-price + IAP apps, but not the free + IAP model mentioned in the thread you're replying to.
Free + IAP seems fine, and it's probably been the most popular PC/Mac software sales method since the 90s.
- potatolicious 14y agoThis impacts free + IAP models also. Here's the classic use case: 1. User gets a shiny new iPhone. 2. User installs my (free) AwesomeApp on new device. 3. User is missing premium AwesomeApp features, is now confused about why. 4. User goes to IAP part of app and tries to recover the IAP/premium features, except Apple's UI here would lead user to believe they are being charged for the IAP again. This is often followed by: 5. User contacts support and is very confused. Support cannot verify whether or not user owns the IAP, because the App Store is a black box and we get no information about purchasers.
- idunno246 14y agoIsn't that what the restoreCompletedTransactions api is for? It's the fault of the app developer for not using it, and forcing the user to go through the purchase flow again.