Navigation advice

Need help
1

hello bubblers,
a quick question please about a one page app navigation.
i am relying on parameters and mostly RE floating groups.
what is the better option,

  1. to unify all the (GO TO PAGE>send more parameters) to only one workflow in a RE custom event, so when user click any button it will trigger the custom event and send parameters to it?
  2. to just make every button do (GO TO PAGE) as usual?

i thought the 1st might be clean but ended up feeling i might just made it more WU.
Thank you

2

Bubble has the go to page action to allow for send to ā€˜current pageā€™ or ā€˜dynamic pageā€™ā€¦with single page app can just always use ā€˜current pageā€™ but it doesnā€™t allow for ā€˜data to sendā€™ however, since it is a single page app there should not be any page content type set, so no need to send data and instead just sending in the parameters. However, there is no way to send dynamic parameters, but if you only have the same set of parameters for every navigation that should be fine.

Do not try to over-engineer stuff in order to feel like it is ā€˜more modularā€™ and that you are setting something up as a one thing to do all stuff as when those require multiple conditionals it can actually make things more complex and much harder to debug. I personally just made a decision to add a second button to a complex app just to make the number of conditionals less so that it is easy to debug (mostly because the new workflow tab is really poorly constructed and makes it really hard to keep track of things with lots of conditions).

This is likely easier, so faster to develop and easier to debug and maintain.

But this is more or less a personal decision to make as Iā€™m sure there are developers who will opt for number 1 and others who would opt for number 2. Just do what works best for you and makes your life easier, and in my experience, number 2 is that option.

1 Like
3

Thank you @boston85719 ,
Yeah what i am actually using is
Go to current page> keep parameter &send more parameters.
My paramas are things like
-Page (shows groups that act like pages).
-Tab ( shows groups inside pages).
-Show ( when just showing a floating above whatever exist).
And some more to show specific chat-id etc.
I managed to unify these parameters as option set.
In option (1) i was sending paramters to custom event ( all the possible parameters) from every button then the custom event would fill the go to current page from these data, but surly thats not a WU saving lol.

My concern was if its normal to have ( a lot of ā€œGo to current pageā€ workflow) and if its normal thing.
I will take your advice and go with number (2)

4

This topic was automatically closed after 70 days. New replies are no longer allowed.