#brlx_best-practices

1 messages · Page 1 of 1 (latest)

remote burrowBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1412291901562032221

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

fathom blaze
#

hi there, could you share abit more on what you meant by "hybrid app"?

spiral pasture
#

Hi, thank you. So the app wraps a webview on both android and iOS. The main logic runs in the web browser inside the app as a single page application, and is the same for both platforms. The webapp's resources are shipped together with the native app. The webview is loading them from localhost inside the app, which is our issue that we want to solve.

fathom blaze
#

We don't have official docs for webview integrations, but based on what we've come across, Apple Pay works in webview but Google Pay does not.

#

We generally recommend directing customers to the actual mobile browser (like Chrome or Safari) for these payment methods to function as expected

spiral pasture
#

Do you have any specifics about how others make Apple pay work, and what the problems with google pay are?

fathom blaze