Handling in-app-purchases, cross platform

I know that in-app purchases are required to unlock app features. Because it’s a digital asset that only exists in the app, we are required by Apple and Google to use in-app purchasing. (correct me if I’m wrong)

However, if I unlock features while using the iOS version, and then I switch over to the Android version of my app and log into the same user profile, should those features still be unlocked?

I appreciate the way Adalo lets users log in using any method to get to the same user profile (email vs Apple vs. Google login options). Regardless of the authentication, it still logs me in as the same user.

However, I wonder what happens when I move across platforms. If I buy on platform A and then log into platform B, wouldn’t it violate platform B’s terms if I’m benefitting from something that requires payment?

We’re implementing a freemium model where free users can do certain things (with limitations) and premium users can do those things without limitations, plus some additional features that free users cannot do.

I expect that I would set flags in their account (Adalo user collection) so that the capabilities would effetively carry over from platform to platform (because it’s the same user). BUT, it almost seems like this would be in conflict with the Apple and Goolge contract, correct? If I buy it from Apple, but then benefit from it on Android…

How is this scenario resolved?

Do we have to force them to buy on each platform? If so, how do we keep track where to enable features and where not to?

Personally, I’d love to just set up a Stripe checkout and bypass the high fees But from what I read, it doesn’t sound like this is enough to justify bypassing their IAP.

Am I missing something?

It’s fine- buying something on one platform doesn’t mean you have to purchase it again on the other.

Apple and Google take their cut at the point of purchase. Moving to the other platform the user has already purchased the product so nothing needs to happen. It’s classed as “consuming” an existing product.

Thanks @speakupboy That is the ideal answer because it removes some complexities.

However, does this still apply if we sell the upgrade on a web application? The scenario would be that I have the same app as native iOS and Android, but also have the app on the web. So while IAP works on those, I’d have to set up a standard credit card (such as stripe) for the web app. I just want to make sure that all scenarios work in this use case. Thoughts?

@deetee yep- just use stripe for the webapp.

Here’s how you can look at it: Apple and Google are getting paid commission for sales you make in their appstore “marketplace”. You sell something through there they want their cut. If it’s a physical item then not - because in that scenario you are just taking payment for a product a customer is buying- the app and the purchasing action are merely ways the customer conducts the purchasing transaction. Whereas digital stuff (games, subs etc)- the app IS the product- so they want their share for hosting it.

If it happens elsewhere then you can get paid elsewhere and you don’t need to pay their cut.

@speakupboy That is a great illustration for me. I appreciate you taking the time to spell it out that way. Thank you.

Would you mind taking a look at my other question too? It’s similar in nature, but very different in that what the user is buying is actually something that is administered by multiple people. Using your logic for the above question, maybe it would also apply in the scenario I lay out here?

Thanks again!

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.