With Windows 8.1 your app can have consumable in app purchases
If you are looking to make money with your app, there are a few models that can be effective:
When you built an app in Windows 8 you could do all the choices listed above, except consumable in app purchases. Developers had to come up with creative workarounds such as durable purchases that expired at the end of the day to try and create a consumable model. Well, good news! In Windows 8.1 consumable in app purchases are now supported, no more workarounds required!
For a complete explanation of how to implement consumables
But just to give you an idea of what’s involved, here's the basic flow for Windows Store commerce in-app purchases:
When a user decides to make an in-app purchase, the app calls RequestProductPurchaseAsync to initiate the transaction with the Windows Store.
When the transaction is processed, a PurchaseResults object is returned to your app. This object contains the purchase result, the transaction ID, and the full receipt.
If the returned PurchaseResults indicates that the purchase was successful, your app can provide access to the purchased assets.
For a consumable in-app purchase, the app reports asset-fulfillment status to the Windows Store by passing the specific transactionId to the ReportConsumableFulfillmentAsync method.
Note Your app should also use the GetUnfulfilledConsumablesAsync method to check for any unfulfilled consumable in-app purchases. This method is useful for checking for transactions that may not have been fulfilled due to interruptions in connectivity or other issues, so that you can make sure your customers aren't blocked from making additional purchases.
If you haven’t done it already, update to Windows 8.1 today and make sure your apps are the best that they can be!
Don’t forget, if you are a student you don’t have to settle for the Express versions. Use Visual Studio Professional to build your apps courtesy of DreamSpark!