Modeling In-App Purchases Inventory
Time-Limited in-App Purchase
I want to let some non-consumable iAP items just be sold during a particular period of time. Also the user who purchased these items still can restore and use it after the time period has elapsed.
Creating time-based in-app purchases (iAP) can be difficult. First all iAPs would need to go through App Review, hence they would need to be available before your app is live. Second is that there’s practically no way for the app to differentiate the app review environment versus the actual production environment – nor does Apple want you to.
But what if I say it can be done? What if you can have a non-consumable iAP, pass it through app review, and only made it for sale only during a specific period in the future? Interested? read on.
All About In-App Purchases
Future-Proof Your Data Persistence
How to Sell watchOS Applications as an In-App Purchase
Which Database to Use for My iOS App?
How Developers can Draw Icons for iOS Apps
Eleven Books and Resources for iOS Developers to Get Started on UI/UX.
Swift Snowflake ID Generator
Trying Core ML with Swift Playgrounds
A Swift Promise
Should You do Free Work to Get Hired?
Is Your Server Ready for iOS 9 and El Capitan?
Apple’s latest operating system updates – iOS 9 and OS X El Capitan – are enforcing stronger network encryption. This is wonderful for users – however it could mean extra work for developers and system administrators.
In short, applications are strongly encouraged to use HTTPS, TLS 1.2 and perfect forward secrecy. You might be saying to yourself, “We’re already serving through HTTPS, so we’re good.” As it turns out, it may not be that simple. It isn’t for Microsoft and you could be affected as well. Yes, at least one of Microsoft’s web services isn’t yet up to Apple’s security standards as of this writing.