In-App Purchase Project Properties

Toolset: Project and Pages

The In-App Purchase (IAP) Project Properties window allows you to setup products that can be purchased from the app. It requires customizations in the stores you want to connect (Apple and Google Play only at this moment) that are out of the scope of this guide. Below, a quick overview of the process:

Understanding IAP

IAP is complex mostly because it does not allow you to test your application in the Simulator and, part of the code needs to reside in Apple or Google’s servers. As several “how-tos” mention (see some below), you are going to spend more time working in Apple/Googles’s side (configuring profiles, etc) than with Kwik.

Start reading this great walk-through from Troy Brant’s  (the code part is not important as Kwik will handle it for you):

  • Basically you will need to create a Unique App ID
  • Create a new provisioning profile
  • Add you application to iTunes
  • Upload your app binary (even if it is not finished) – you need a binary to create a product
  • Add your product(s)

IAP in Kwik

As mentioned before, Kwik only works with internal asset purchases. Considering it uses the concept of pages, imagine that some pages will be unlocked only when the user purchase them. You may have a free storybook that allows the reader to read until the middle of the story. To finish it, he/she needs to buy the rest of the pages.

In-App Project Properties

When the IAP Project Properties button is pressed, the following window appears:


All previously entered products will appear in the list. To delete a product not desired anymore, select it in the list and press the trash button. To add new ones, just press the + (plus) button. Doing so, the following window appears:

  • Name: enter a name for your product, as set in the appropriated store (we strongly suggest you to have the same product name and id if you are connecting with more than one store);
  • ID: is the ID created in the appropriated store (this is the string used to get your product from Apple/Google’s store;

6 Comments

  1. Luc Adriaens

    Are there plans to work with EXTERNAL asset purchases in the future? With internal assets, the ‘container’ will be unnecessary big when people download the app but don’t buy additional content.

    • Kwiksher

      Honestly, no. Which scenarios do you see covered with the external asset purchases? The main issue here is to handle all the things externally to Kwik (users must need a website with the correct permissions to download items, they must create a webservice to validate which items can be downloaded, etc). In Kwik, the complexities can be gigantic due the several possibilities (someone may want just to download an image, for example, a weapon. others may want to download an entire scene, …). For these really personal yet complex situations, you have the ability to add your own external code.

  2. I’m using Kwik 1.9.8, and have an issue with in-app purchases. All is set correctly, as the purchases are functioning, however, my issue is lag. Once the user presses the ‘buy it now’ button on the app, there is a HUGE lag before the apple ‘confirm purchase’ message is displayed. This means that the user has no feedback that the button was pressed. Am I doing something wrong?
    Thanks for any help.
    Best,
    Robert

    • Kwiksher

      Robert, there is not much to do in this case as the lag depends on a series of factors like Internet connection, apple’s approval, …

Leave a Reply