Is this production ready yet?

[mikecfisher]

Hi @hyochan thank you for making this an expo module on the new architecture this is a great idea.
I have been following the progress from react-native-iap to expo-iap.

I know you have been having some personal issues that are slowing down progress on this. Totally get that and wishing you the best of luck.

I am building an expo app on the new architecture and need to implement IAP. I was seriously considering using this library but this will be in an app that I am rebuilding that has a user count in the 7 figure range. In the thread on the old repo you said proceed with caution as it's still under development. So I just wanted to check in to see if this is ready to go.

Thanks for making this!

[hyochan]

Hi @mikecfisher,

Thanks for reaching out and for the kind words! I’m glad to hear you’re considering expo-iap for your project.

To answer your question: expo-iap does build on the react-native-iap codebase, which means it inherits a foundation that’s been tested to a decent extent in the wild. That said, while it’s in a usable state for many cases, it’s still evolving. You might run into various trial-and-error moments, especially with edge cases or specific platform quirks. These are the kinds of things that will need ongoing contributions from the community to iron out fully. For what it’s worth, react-native-iap is in a similar boat—battle-tested but still a work in progress in some areas.

Given your app’s scale (7 figures is impressive!), I’d say it’s close to production-ready for simpler IAP setups, but I’d still recommend proceeding with caution. If you’re able to test thoroughly in a staging environment and potentially contribute fixes or improvements as you go, it could be a great fit. Otherwise, if you need something 100% rock-solid out of the box right now, you might want to weigh it against other options or keep an eye on progress here.

Wishing you the best with your rebuild, and feel free to let me know if you have more questions or run into anything specific—I’d be happy to help!

Hope you can try version above 2.2.3