Native App Navigation - controling with URL parameter is not good?

Clicking “This page is native app”, Bubble says do not use any “go to page” action.
However, without “go to page” action, an app can’t be navigated by URL parameter. And without navigating URL parameter, “go to previous” action should be extremely complicated. Although I know I can store Page History in Custom State, It must be very complicated or nearly impossible storing Data History attached to each Page History. Only simple way I found is storing history Data thing but this can’t work in no signal situation and should waste a lot of workload.

Should I really convert URL parameter navigating into others like Custom State and/or Show/Hide action navigating?

On the main page load, display or animate in only if the URL parameter is “Example.” Alternatively, set it to be visible when the URL is “Example.” Avoid displaying the message “This page is a native app,” as it is intended for a native look when accessing the page from a bookmark saved on your phone’s desktop, which is unnecessary if you’re wrapping the app for Android or iOS (search for website-to-app services on Fiverr).

I’m not sure why Bubble would say do not use go to page action if the page is set to be native app…also, there is no native app functionality in Bubble at the moment, so I do not know why there would be an implication of a native app page.

You should test it…if the go to page action still works on a page that is set to be native app, go ahead and use it. If for some reason you are not able to use go to page action, you can use navigate open external website or a link element…both of which you can still structure your URL to have parameters, but need to do so manually with go to external website, but link element works similar to the go to page action.

Does the native app page setting cause the URL to have the value of Example?

1 Like

Search for “PrikaKidz” on the Play Store (and soon on the App Store when it’s ready for publication). It’s one of the apps I’m currently working on. Take a look at its functionality. I developed it as a one-page app, utilizing URL parameters with page names assigned values for each group I wish to show or hide. Additionally, I implemented animations. I made certain adjustments in the Android Studio code to disable certain features and enable others to ensure seamless functionality like a native app, including permissions, notifications, and uploads.

I believe Bubble doesn’t recommend using parameters for page changes because it triggers a reload animation whenever the URL parameter changes. However, I found a workaround for this by disabling loading animation in my wrapping code, and it works great!

1 Like

Thanks. Actually, my wrapped native app is working very well so far with navigating URL parameters. I’ll see for a while if everything continues to work…

We’ve created loads of mobile apps on just one page. There’s no real change on tagging the page as a native app, you only ask the system to flag you whenever you’re making something like going from page to page and design dimension, etc etc…

Plus the only true benefit is having native ish animations on elements/groups. Go ahead untag your page as a native app and use the go to current page function.

1 Like

You encouraged me a lot! Many thanks!

1 Like

Hope you can keep building your app, please keep in mind that every software you build of course has to be within the guidelines, etc etc. But remember what makes the product great is you and you are the builder, just build it your own way no need to be perfect on the first try.

1 Like

No it doesn’t. When you use the go to page workflow action and are navigating to the same page the user is currently on, just simply to change URL parameters, the page does not reload, and in fact custom states are not even lost. Whatever animation action you set up might have just needed it’s condition on when to trigger changed so it wouldn’t animate each time the URL parameter changes.

@boston85719 What about something like this? :slight_smile:
Untitled Project


just downloaded the app, and i first want to say, WOW. Swell job on the loading times.

The splash page opened up near instantly in NYC North America.

What really amazed me was the loading screen? How’d you get it to do that? The loading screen felt real, and the entire app loaded in, in about 3 seconds.

For navigation, are you displaying the loading screen as the last group before going to the main app home page?

Is it a gif? Video? Smart plugin? I’m very intrigued.

It kinda half started to do loading (white circle appear on top of the app for a split of a sec) then dissapear. I know changing parameters dont actually reload whole page. I fixed this with some coding in wrap.

Loading screen goes on to circle trough all parameters displaying all groups that exist and to load everything in the background, after finish it shows main page. I did explanation on the forum few days ago. Search “Real Loading for one page app” this loading makes app run very smooth.

check app on and watch parameters in address bar change.

Thanks for good words.

What about it? You are using path list item instead of parameter, but I’m not sure what you are asking.

You can achieve that by using plugins or even css samples to manipulate the front end.