Basic In-App Purchasing question

[Don]

I know I should be able to figure this out from the docs, but I'm having trouble grasping a basic concept...

Say I have an app with a png background. I want to sell different background images via In-App Purchase. Do I:

A) Create some sort of package / bundle containing the new png files and submit it to the App Store. Users who purchase a new background via In-App Purchase receive the "bundle" from the App Store. My app looks in a "download" location for the new images.

or:

B) Only *define* the new background as an In-App Purchase item in iTunesConnect. User purchases the new background via In-App Purchase. My app then must contact my own server to retrieve and store the new png file on the user's device.

Thanks, Don

[baja_yu]

B.

For any content you want to provide that is outside the bundle, eg. new images, you need to host it and provide a mechanism for its delivery to the app. The store only processes purchases and verifies receipts for you.

[Don]

Thanks for the quick response.

Reading through Apple's docs for Feature Delivery, under Built-in Product Model, it states:

"Content-driven applications can use this to add new content without modifying the source for your application."

Which led me to believe I could submit an In-App Purchase "resource bundle" (sans any executable code) which would then automatically be delivered by the App Store.

Now, looks like I have to investigate Content Delivery solutions (our IAP content will be *much* larger than just a few png files).

- Don