-
Hello everyone, we are considering converting our mobile app to a Hyperview app. Before dedicating resources to this project, I would like to inquire about Hyperview's capabilities for handling in-app purchases or other payment methods approved by the Apple app store. I have been unable to find any relevant documentation on this topic. Can anyone provide me with information or advice on this matter? Thank you. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Hi @wjkoh , Hyperview does not have support for IAP or other payment methods out of the box. Support for those would need to be added via extensions (custom behaviors and elements). How difficult this will be depends on the answer to the question: is your current mobile app written in React Native already? If the answer is yes, you could expose your current IAP flows rather easily (custom behavior to trigger a purchase or subscription with a given product ID, and then trigger an event on success/failure). I think this would be rather straight-forward. Another option is to write most of the app in Hyperview, but keep the screens that deal with purchases as React Native implementations. If your current app is not written in React Native, then you can expose the functionality in Hyperview by using the React Native IAP library and wrapping that as extensions. I don't have experience with IAP myself, but my understanding is that the flows are quite complex and take a lot of time to set up properly (see this diagram). So please keep that in mind when considering if converting the entire app is right for you at this time. |
Beta Was this translation helpful? Give feedback.
Hi @wjkoh , Hyperview does not have support for IAP or other payment methods out of the box. Support for those would need to be added via extensions (custom behaviors and elements). How difficult this will be depends on the answer to the question: is your current mobile app written in React Native already?
If the answer is yes, you could expose your current IAP flows rather easily (custom behavior to trigger a purchase or subscription with a given product ID, and then trigger an event on success/failure). I think this would be rather straight-forward. Another option is to write most of the app in Hyperview, but keep the screens that deal with purchases as React Native implementations.
If …