I would need some advice here.
I have an app on the appstore for some time.
Let's call it app Basic. Which sells for 1.
I will introduce soon a more powerful version, with Watch support.
Its name will be app Pro, with a specific icon. It will sell for 2.
I considered several options for sale, notring that I want to keep both versions in appStore.
Option 1:
Have the 2 versions sold independantly.
Great for the one who buys directly Pro or just wants Basic because he has no need fopr watch app.
Problem: user who paid 1. for basic will have to pay 2 for Pro when he does not need Basic anymore. At the end, that means that Pro costs 2. or 3. depending how you purchased.
Option2
-> Is there a way to discount on the appstore (I mean, no specific feature in the apps) if user already bought basic ?
Option 3:
Sell Pro through IAP of 1 in Basic
-> But that will force user to buy first Basic, then IAP for Pro to install a second app.
I am certainly not the first to have a dual version scheme. Are there other better options ?
>...2 versions for iOS app, the second coming with a companion Watch (but can be used alone as well).
That's clear now, thanks.
In the past, I believe App Review has on occasion politely pushed back against both a basic and pro app distribution scheme, especially when they are otherwise identical as per basic. I am unable to find any evidence that IAP'ing a companion app is either allowed/prohibited. I'd wonder if there is crossover with extensions and widgets, tho...
My opinion in your example, given basic is already in the store is that 2 apps, where one adds a watch companion component, would be ok, but as always, only App Review knows. Might be worth checking the store for prior art, and, pinging support for their opinion.
Ken
