Design tips for StoreKit in iPhone OS 3.0? -


I am going to implement StoreKit in an iPhone application and want to know that there is any experience available already Can you say that any damage or trap in using StoreKit?

I know the API is new - but there are some premium content in my app, which I want to ask users to pay, and this is an ideal way to do this - different payment on your membership Instead of giving directions to the website.

I also assume how app is installed in the App Store in the App Store, to make it clear that the app is free to install - but you have to upgrade for some functionality Will happen.

UPDATE (from comments): You can not convert a free app into a paid app - so the user has to first charge it for the store kit API additional software.

2 Update: Now you can use the API for free - Apple has recently changed the rules


Oak application that uses the Store Kit API , On which I can model user interaction?

Implement the storekit to think about things:

  1. When you restore the [code> [[SKPaymentQueue defaultQueue], then the complete transaction is included]; Sometimes you get the (zero) payment QueueRestoreCompletedTransactionsFinished: (SKPaymentQueue *) - (zero) Payment Qi: (SKPaymentQueue *) Queued updated transaction: (NSArray *) transaction Call back before the callback (and sometimes long before ) (sometimes the transactions are also missing.)

  2. < P> Sometimes when you add a purchase with [[[SKPMantQue Default Qi] Ad Payments: Payment]; Transaction has been removed from the queue and only you get the feedback: - (zero) Payment line: (SKPMentQue * *) Queued transaction: (NSARRA *) transaction

  3. A wide variety of error messages have been returned in the user's cancellation and some error status SKErrorPayment returns the canceled error code. Specifically:

    • If the user canceled the hit, the transaction error is zero with "You have already purchased this product"
    • If the user 'sign in: [using the existing account Please] [Create new account] [Cancel] 'is an error code, then withholding with the signal with SKErrorUnknown.
    • If the user hits [OK] instead of canceling the signal when prompted to enter the password and the password is not entered, the error code SKErrorPayment has been canceled.
  4. Do not forget to apply another SKRequest callback:

    - (zero) request: requested (SKRequest *) FailWithError


Comments

Popular posts from this blog

c++ - Linux and clipboard -

Visual Studio 2005: How to speed up builds when a VSMDI is open? -

booting ubuntu from usb using virtualbox -