I am implementing newsstand application,we are selling issue for each month either by subscription or by direct purchase for old issues(price is different for all issue)
I have already done with subscription (auto renewable) and its working fine.
My Concern is about direct InApp purchase of old issues.
Which type of InApp purchase best suite for my app consumable or non consumable?
If I choose non-consumable type I need to create new product id for each issue(issue are dynamic to that will be lots of product id i have to create)
If I choose consumable type I can use same product id for all the issues - non need to manage InApp from iTunes but in this case Price for all the issue will be same.
My Question is, Is there any solution using which I can handle InApp purchase of dynamic issue where price for all item is not same and also don't want to create new product id for new issue.
I have found solution for above situation....
We must use non-consumable In-App Purchase for such kind of applications.
If we use consumable In-App Purchase for magazine issue, Apple will reject your application.
And Ya, We need to create CMS which is responsible for managing product id.
Let me know if anybody have any issue in Newsstand app.
Thanks
Related
I am using MK in-App Purchase and I want to make an application that have (let's say some books) and the books are getting added over time and each book the user have to buy it individually so how can I add with every book in-app purchase key for it without make an update for it.
I can't figure out a way so I need a step by step or a link for a tutorial for that.
I'm not sure if this would be the best way to set this up but if you are selling the books at certain price tiers (e.g. 1.99, 2.99, etc) I would set up a number of In App Purchases to reflect each price tier. Then when the user purchases a book match the appropriate tier to the book purchased.
You can set these up using the tutorial you already linked to in your question.
You will need to update your current app to accept in-app purchases and process them accordingly. After adding support for in-app purchases, you will need to re-submit your updated app to Apple.
I have personally used UrbanAirship in several of my projects. They offer tutorials on how to implement their in-app purchase solution into your app, which is quite easy.
I have already visited this thread
iPhone + In App purchase testing
but the solution of creating a new account each time you want to buy the same item is extremly tedious.
There is also the solution of creating a new product or I guess by changing the product identifier should work too but this is not a very friendly and productive solution as well.
So, is there any documented way of un-purchasing and than purchasing again a product when testing InApp purchase with sandbox?
You really don't need to un-purchase your items, as re-buying them on the same account really gives you the very same transaction, minus the money.
There is no way of doing this, other than creating new users.
We want to sell digital content through subscription model in our app. Is it possible to support a subscription bundle? Let's say content in question is magazine subscription for $0.99 a month. Is it possible to support a bundle of subscription such that user can subscribe to any three magazine by buying a bundle for let's say $1.99? Or is it possible to support eat-all-you-can model - $3.99 for subscribing to all magazines in our app?
According to the official documents from Apple, yes you can. What you need to do is design your iAP store and items according to Apple's requirements.
Getting Started with In App Purchase
on iPhone OS (Version 2.0)
...
Subscriptions
Subscriptions and subscription
renewals to content or services can be
offered to customers for purchase. You
can offer customers the opportunity to
renew their content or service
subscriptions using In App Purchase,
but be sure to define a reasonable
renewal frequency to avoid bothering
users with unwelcome reminders. Be
aware that you are responsible for
both tracking subscription expirations
and for renewal billing; the App Store
does not monitor subscription duration
and does not offer an automatic
billing mechanism. Be sure to indicate
when an item is a subscription when
entering its product information into
iTunes Connect.
Both of these features are supported, they are called consumable and non-consumable in-app purchases.
I am making an in-app purchase application for bulk of quizzes. I have all the information, graphics and data set of quizzes on my server. I want user to purchase quizzes with in-app purchase and want to transfer all the related content of purchased item from my server to application.
Now, apple is asking me to submit binary while adding in-app purchase item. Is this compulsory? For all kind of products (Consumable, Nonconsumable & Subscriptions)?
What if I want to manage the contents(graphics, database for that quiz product) of the product on my server not on itunes connect?
Help would be appreciated.
Thanks.
You don't have to submit binaries. In fact, it's not even possible. In-app purchases only have a product ID, a description and a price.
Also, be aware that you can't send new application code to the device via your web server. Only data can be sent.
I have a website which sells a product to the user (downloadable). I am creating an iPhone app and want to be able to sell some of the products using the 3.0's in-app purchase.
Now the documentation mentions that anything you want to sell has to be uploaded to iTunes Connect and approved by Apple. But I want to be able to keep adding products to be sold by my app on a daily basis.
I have a web service to get the list of products from the website. Is it possible to include in-app purchase to let user buy this stuff from within the app but without having to add them to iTunes Connect?
As I understand it, no - all the things you want to sell via in-app purchase run through a vetting process similar to that of the apps themselves. Apple won't allow, for example, a "photo of the day" application if you can in-app purchase pornographic photos to be sent to you daily.
What you could probably do is submit your app with a backlog of in-app purchases, five or six days ahead of time, then consistently be submitting your daily items ahead of when you want them to be available. Not sure how reliable the review process is, or whether this will work for your situation - just a thought.
Nekin,
I think you have to use the type as consumable (in app purchase) product as each time the product has to be purchased. Once you purchase a book, then you can mark it as purchased in your local app database and that way the user need not buy the same book as you can check it in the local app database before connecting to the in app purchase payment request and this way the inapp purchase products can be dynamic and can use as many books but the list of books should be from your server.
You can keep updating the server data with more number of books.
Thanks,
Vijay