Hello forum, I’ve been enjoying the native mobile builder and pushing its limits beyond on-platform capabilities.
However, I did hit a couple roadblocks: in-app internet browsing and return URLs. Curious about current workarounds.
Browsing
When selecting “open an external website” the users is taken to their mobile browser instead of remaining embedded. Hopefully this is only an esthetic matter and won’t prevent passing params, etc. so far it seems that at least API calls relying on app data are working as expected. Interested in what others have experienced.
Return URL
As an example, Stripe Connect’s return URL which allows the user to return to a specific page without your application, like their profile, or home feed, etc. after completing or canceling out of a specific flow and which is usually handled by providing something like “yourbubbleapp.com/return_page” which can be “yourbubbleapp.com/user_profile” or alike.
For native mobile apps the recommended schema seems to point to something like “your-app://stripe-redirect” and wonder if anyone has deployed (I haven’t yet) native apps with Bubble having this sort of requirement.
My current workaround is to have splash screens for both return and refresh URLs notifying the user that they’ve either completed or canceled the flow and that they can safely close the browser tab and return to the mobile app. It certainly works but isn’t the smoothest UX.
Curious what others are doing and glad to share more about my experience with the mobile builder so far, which as been quite positive.
as I get closer to deploying, I should specify that the proper term for what I described about is “App Scheme” as per the docs
This setting defines a custom identifier for your app, used primarily in scenarios where external services need to redirect users back to the app after completing an action. This is commonly required for callbacks from OAuth providers, payment gateways, or other integrations that require redirection to the app.
Should anyone have experience with this exact scenario, I’d like to hear about your experience.
Im in a similar predicament to you, im using the GoCardless API to enable a user to connect their back account, the flow provides me with a GoCardless URL which the user is then redirected to in order to complete their account connection, after which theyre redirected to a URL i specify in my API call to them
But once i pass the account connection in GoCardless’ web estate, i get redirected within the browser, not back to my app in BubbleGo
Take a look at this, first table item “App Scheme”
And here for how to set it
The assumption is that when the app is actually deployed “Go to an external website” will be in-app as opposed to the scenarios we are discussing, which still works, as I described in my original post, but isn’t an ideal UX.
However, and this is important, an unexpected side effect is that by doing so, you will not incur in Apple/Google store fees (15%-30%) so you might elect designing an experience tailored for this.
Why don’t you just store the result in the users database?
When payment or whatever is done and you go back to the url, stor if it’s solved or if a error occurred as a text filed or yes and no field.
Have a condition in the view with the weblink
When current users payment status is ” worked/error” make change to current user payment status = null go back to preview view
I use open an external website and in reality even after the distribution the external browser continues to open.. Where did you read that after the distribution it won’t be like that?
