Moved from: https://github.com/expo/expo/issues/11
Add support for in app purchases to standalone apps on iOS and Android
maybe this is the area expo could monetize somehow? Apple takes a big chunk already, but skimming another 1-2.5% may be okay with some people if the API really does save a lot of implementation time and maintenance for in app purchases.
@arcom: I'm not sure this would resonate well with developers, I think best solution for expo would be to introduce monthly fee for their services (push notifications, apk builds, code push etc..) I'd be more than happy to pay for expo as a tool / set of services rather than In app purchase revenue share.
Also, I assume there will be way more projects using expo that are free / don't generate revenue where expo will benefit more from above mentioned subscription fee.
Never the less, this is an interesting idea.
@ilja: Great points @ilja
@arcom: I am a developer that is 100% for this, say 2% (but not more than that)... it's a small price to pay to expedite/streamline my monetization strategy... @ilja ... look at it this way... this feature does not even have 'planned' status yet, and doesn't seem to be a priority for Expo... if developers all agreed to this 2%, I'm sure Expo would prioritize this into their API asap... and for developers that are rev share sensitive, Expo can introduce a sliding scale where volume thresholds reduce 2% down to like 0.5% or something like that... i think it will be much harder for Expo to monetize on services they have already given us for free (push notifications, apk builds, code push etc..)
@Chris: agreed
@Chris: Yeah. I'll use expo either way, but it would be nice to know expo can sustain itself as an organization.
Payments is the biggest missing feature from expo by far. I wish they'd focus 100% on this instead of stuff like adding haptic api or these other niche bridges. I mean, how many people are building apps that will never need to make money? And I think using the stripe API is against apple policy (but still not sure on this).
This would be awesome! And please include subscriptions
The #1 reason I'll have to detach to Expokit for my current project (and I don't want to, I love Expo!)
I build a standalone app, so I would need this to work with that
Will eventually have to detach because of this - our specific use case is subscriptions
@Brent Vatne just out of curiosity, I'm sure this is on your radar, as most apps would generate revenue through the feature, but how come it is being delayed so much, is it complex to implement?
I need to detach only because In app purchases is not supported. I want to stay with expo!
This has been on the radar for so long, when can we expect this ?
Please please need this. ❣️expo
Guys, we need this feature...
This is really important for those of us trying to get investments of some sort for our apps. Probably the #1 feature I need
I've created one here. I hope this library goes to expo too. https://github.com/dooboolab/react-native-iap.git
@dooboolab: Very cool. Just what I need in the interim. Thanks for posting.
@Jack Kinsella: Thanks. I didn't want to detach from expo app but had too because of this feature.
+1 Essential monetisation method missing from the Expo app workflow
Would love to see this too
It's a must have, would be nice to integrate https://github.com/dooboolab/react-native-iap to expo.
@alan_langlois: I wonder what is holding expo back from doing a wrapper of this for v28.
This is much more important than all other features
@Christ: I think so!
@Christ: Yeah this seems like a huge huge short fall.
Please add support for in app purchase . I think it's very important feature.
@alanlanglois: this one seems to have a more streamlined API with better implementation/integration and better docs, however, it's unfortunately not cross-platform: https://github.com/chirag04/react-native-in-app-utils
@Chris: react-native-iap is cross platform and works great. The guys working on it did a lot of interesting changes lately and this lib is slowly becoming very relevent.
Missing IAP support is the #1 deal breaker for Expo
@Timo Jääskeläinen: Yeah it really opens the door up for people to say "Expo is great but only for apps that don't make money"
Hello,
We are using Expo to create our project. In our project one important topic is in-app purchase. Could you help me
how to implement in-app purchase using expo and what are necessary steps we need to follow to implement this.
@swyan Mitra: You have to detach
I can't imagine any other API taking precedence over this one. Who is voting for bluetooth over this?!
@arcom: :D you are right
This feature is extremely relevant for choosing expo in the future projects.
@Leia: agree... this is the deal breaker for hundreds of apps I'm sure. It's great and fun to see semi-obscure APIs like AR included but not anyway to add subscriptions (and not cross apple).
Can we just get IAPs? There is nothing more important you guys should be working on than this. It’s the only thing that stops me from using Expo. Without it, we’re basically building webpages :P And it’s been a year since I’ve built my first Expo app and still no concrete plans?
@Kjell Connelly: I just had to move an app off of expo because of lack of IAP... I'm using vanilla RN with AppCenter. It's not too bad but it took a couple weeks to get a grip on all the moving pieces.
Is there anything the community can contribute to this one? Planning, research, documentation, development, etc. Please do email me if you need extra help/eyes on this task, i'd be happy to contribute!
I understand Expo removed IAP as Apple rejected apps with the Payment SDK if they did not actually perform any payments.
Would it not be an option to enable or disable the payment SDK with IAP functionality for Androd and iOS incl. Subscriptions with a build parameter or flag?
Expo could keep the current behavior, but for anyone requiring the Payment library, a build flag would allow to include it.
I'd be very happy to contribute on this one. How could I do that?
Is there any update on this? Seems many are willing to contribute?
Any update? This is a huge deal breaker for us.
Any idea if this would become a reality? We are ready to start selling subscriptions through our App, and Apple has clearly stated that they will not allow developer to redirect users the business or developer's site in order to make the purchase or sign up for a subscription. I've read in other posts that this request has been laying down here for months. It is also highly needed for Android Apps. Hope to see it released soon.
Hi guys, can we have an update wether this will be implemented or not and a possible timeframe? We just faced a rejection from Apple and have no clue if we have to ditch expo or wait for this to be implemented.
Really Really need this...
Is there anything I can do to help get this started?
This would be a game-changer for Expo, please increase its priority!
This needs to happen! It’ll enable a whole class of apps that aren’t possible to sustain with a flat fee: games, marketplaces, dating apps, productivity apps, or any SaaS app. Not to mention that Apple has strict rules about going through their payment processor. Without this, Expo isn’t as “empowering” as it claims to be.
@Brent Vatne - Would it make sense to accept some of the volunteers to start working on this ?
@Jesper Madsen: totally agree. the pain of moving out of expo is much larger than to actually work on this
Any news for this?
I believe this also addresses subscriptions?
@ilja: I imagine so but not sure until the work is scoped, you can submit another feature request with subscriptions explicitly flagged :)