Yeah, I understand. The more you use Bubble the more you learn. Most of the things that are hard to do are only hard the first time. The second time it’s quite easy. This is probably one of those.
Perhaps create a new page and play around with custom states. The way they work is that it’s a value that’s stored on the users computer (i.e., client-side in computer speak). Custom states are attached to a specific element on the page. I usually use the page-level element so that I can quickly find all of the custom states on the page and don’t need to figure out which elements have custom states.
You can use workflows to change the value of the custom states. You can also set things to happen when a custom state changes. One specific implementation is if you have a group, on the conditions tab (click edit for that group, then it’s the 2nd tab) you can set a condition that basically says, “When 's <custom-state-name” is " and then select a property to change “this element is visible” and check the checkbox so it is yes. Then, also set the default for that group to be hidden (on the edit tab). This way, that group is hidden unless the custom state equals that one value.
You can do the same for the other groups as well. (Try it with just one before you spend time coding the others). Then, you’d want to set-up a workflow szo that when a user clicks, say, a button to go to the next view you run a workflow that changes the hidden state’s value. Changing the value will automatically hide the current group that’s visible (if you set up conditions on it correctly) and also show the new group you want to be visible (if the conditions are set-up on that new group correctly).