Say, in my app, I offer books.
Correct me if I am wrong, book are non-Consumable products.
Say, every book costs 1$. Do I need to have multiple products in itunes? Or can I have one product and repurchase it (reuse it's product code), for every new request to buy another book.
No you can't use the same ID for every book, you will get refused with a warning message when one non-consumable is resold.
Have a look at the overview of in-app purchases below:
https://developer.apple.com/library/ios/#documentation/NetworkingInternet/Conceptual/StoreKitGuide/APIOverview/OverviewoftheStoreKitAPI.html#//apple_ref/doc/uid/TP40008267-CH100-SW1
Related
i know how to create and use product IDs for a single non-consumable IAP.
I have searched for more than 2 days but can't find the answer.
my app has about 1000s list of books. when users click on a book cell(table view cell), an IAP calls and the user can pay for each.
is it possible to create product id dynamically in code at run time?
if not what is an alternative way to do to create a product id for each book cell?
Note: I don't want to use a credit system, because I want to sell each book individually.
Thank you
Can I create one in-app product for, say, some music, and then vary the exact track based on a database key?
So the user would buy a music product but the app keeps track of the exact data which comprises their instance?
As #Paulw11 said in his comment above, you can setup a consumable product ID that offers one or more "credits". Using the concept of credits is the only way you can dynamically allocate products to purchases without adding a product ID for each song in iTunes Connect.
Consumable products can be purchased multiple times, so allocate credit or direct the user to select the song once they buy the product. Be sure to call finishTransaction to "consume" the purchase, otherwise the transaction will remain in the queue and additional purchases will be blocked.
Be warned though, consumables are not restorable; if the user deletes and re-installs the app all their songs will be lost. One way to deal with this is to keep a server-side registry of songs a user has purchased, which means you will need user management and authentication etc.
Here's another stack question relates to yours.
After going through number of question still i haven't receive any to the point solution. In one of my Iphone application i'm using in-app purchase payment method. As per requirement i have created consumable product but after first purchase it gives me a message on second purchase that product is already buy for the same product. Requirement is something like this, for one added item user can buy three different time slot and for every slot user need to pay. So for item(I1), user add timeslot (T1) and pay for the same, then add timeslot(T2) and pay for the same.
I am having an issue implementing the kind of in-app purchase that my application demands, Basically we need to sell story books but the books and their prices are not fixed as the book list comes from some server. The price range is fixed i.e a book will be having price from this 3 prices(0.99$, 1.99$, 2.99$).Apple demands the purchase of books to be a non-consumable purchase, the issue is that we create 3 in-app purchase that I mentioned but there can be any number of books having the price 0.99$ but once we have purchased a book with in-app id of price 0.99$, if we purchase another book with same in-app ID it will say you have already purchased this item.We just want is to create a single in-app id and use them with multiple books of same price.Please help me out with some solution regarding this issue.
For non-consumable in-app purchase you will need to create an in-app purchase code in iTunesConnect for each product. You can't use a generic product code as content purchases need to be restorable (and you would also have the problem that you pointed out of not being able to purchase more than one product at each price point).
Each content in-app purchasable item needs to be submitted to Apple for approval.
Maybe you can try to let users purchase virtual currencies in your app. Then let them use those currencies to buy your books. In this case, you don't have to worry about the dynamic price and all you have is a single IAP item(currencies). But your server has to handle the purchase history carefully.
Not sure if this helps, i am dealing with the same problem in subscription items.
You can create three consumables IAPs; a 'One dollar book' consumable, a 'two dollar book' consumable and a 'three dollar book' consumable. Each consumable can be used by the user to download (or otherwise secure access to) one book in that price category. Alternatively you could just sell Tokens and require that the user cash in 1,2 or 3 Tokens to buy a book in each of the three (or more) categories. You would need to keep track of the user's purchases or create some way of allowing the user to transfer rights from one device to another device. iCloud (each App has a key-value object) is good at managing that.
From my understanding, Windows Phone now allows in-app purchases. I would like to empower my users to signup for one-of-three subscription levels within my app. However, I do not understand how to enable this type of scenario. I see the option to add an "In-app product". However, in my case, I'm not sure of the following:
Am I offering one product or three separate products (one for each subscription level).
I don't understand the "Product Identifier" is this an identifier for the subscription or the identifier of my app? If its the former, shouldn't I just toss a GUID in here?
Thank you,
It may be worth taking a look at the overview on MSDN - your product identifier is the one you submit (as a person) via the development dashboard - it's also the one that your app can enumerate to see the list of available products, and the product id you'd use to purchase.
As far as I'm aware, you cannot have products that are (for example) £10 per month though - of course you could do something like have bundles on a pricing structure that exchange for something within your app, maybe £5 for 5 music downloads, £9 for 10 etc. rather than "a £10 per month for unlimited" (difficult to give a generic example though)