Hey ​@daniel-reiling 

Thanks for reaching out and best of luck with the hackathon!

If you haven’t seen it yet, we put together a blog post on how to add in-app purchases to a Bolt-generated Expo app that walks through the current options and limitations.

We’ve also recently updated our docs with an Expo-specific setup guide under the “Install SDK” section. That should help you get started with a custom dev build if that’s supported in your flow.

Let us know if you hit any blockers - happy to help you get unblocked quickly.

Best,

Thanks for the info, ​@guilherme !
 

The blog you shared confirmed my understanding that Expo Go does not support integrating RevenueCat, since RevenueCat requires native code. So to use RevenueCat, we’ll need to transition to using Expo Development Builds. That definitely helps clarify and guide our path forward.
 

The tricky part is that Bolt.new (from what I understand) only supports the Expo Go workflow and not Development Builds. So it puts us in a bit of a bind—we need to choose between continuing with Bolt OR switching to Development Builds to support RevenueCat, but then losing Bolt compatibility. Our ultimate goal is to build a subscription-based mobile app using RevenueCat, but we’re a bit concerned since the hackathon requires the app to be built “mainly in bolt.new”
 

That said, this is probably a question for the hackathon hosts. You've helped clarify the technical path forward with RevenueCat—thank you!