Built in mobile device 'back' button

Hi, I’m creating a mobile app so instead of navigating between pages, I use groups that show up and hide based on their custom state yes/no. After testing my app (which will be available on the app store and play store) in web browser, I started to wonder; how the built in mobile device ‘back’ button will impact my app’s behavior? In the web browser it might have different impact than it will have as an app, I hope that after clicking on this button it’ll just make a 1 step back and don’t navigate to the last page because there is only 1. Can I have any influence on wat this button will do inside my app or no?

If you set up the app properly and use URL parameters instead of custom states for the visibility of certain groups and changing views than the mobile browser back button will function exactly as it should.

How can I use the URL parameters without ‘go to page’ action? Because that’s the whole problem; if I’d navigate between the pages on mobile version it would slow down the application. Thank you.

Use “go to page” —> current page

there’s no loading screen. URL parameters keep you on the same page, but they show and hide groups based off your URL.

Ths is essentially how you build a single page app shell

Oh, thanks a lot!

Okay, I’ve got problem with this. I already did something similar in order to change the language of my app (app text) but in this case I have no idea how can I change the URL parameter basing on the trigger ‘element is clicked’, what should be a parameter key (should it be the same for all the groups to show and hide in order them to hide when this value changes?) and what should it be equal to (in my previous experience with URL parameter it was equal to dropdown’s value). I’d really appreciate help, thank you.

Parameter key can be anything. It’s just an identifier. You can name it, “steps”

In order to change the parameter key after the element is clicked, use the “go to page” workflow and just send additional parameters. The additional parameters will have the same key but a different value.

The different value is contingent on whatever group you want to show the user next.

You can use the dropdowns value if that is the group that decides what page the user sees next.

This thread should be useful as I go a bit more in-depth. Please let me know if you’re still having trouble and I’ll try to explain it better and // or try to link another relevant thread to help you out.

Stumped On Start over/Go Back Button - Need help - Bubble Forum

Okay I think it works! I thought that the key’s value has to be a dynamic expression. Thank you very much!!

One more thing; if I have a floating groups from which the user can normally go back to different pages (depending from which one the user navigated to the floating group) that are normal groups would it be better if I’d have a different key for floating groups and when the user clicks ‘back’ (the back in my app not in device) the floating group would just hide (because floating groups key = empty) showing the normal group?

Sorry just seeing this

Honestly, if this floating group is meant to be seen at the same time as your navigational groups, then yes.

For example, let’s say you’re building a social app. Your groups consists of

Home Page

Search Page

Profile Page

Notifications Page

You would use the same key for all of these pages.

Now if I’m on the home page, and I want to show a floating group while retaining the home page in the background, then I would use

Go to page, send current parameters checked

send additional parameters checked

additional parameter key would be something like

floating_group_visible = yes

Then for my floating group, I would have it set to conditionally show itself only when “get floating_group_visible from page URL = yes”

So now I have a floating group showing itself over the home page. The minute the user hits their back button, the Floating Group will hide itself.

The only time I would use the same key as the Navbar groups is when I want my floating group to function essentially as it’s own page, thus, hiding all the other groups around it.

Now everything works as it should, thank you!

1 Like