For Native apps: Do you have to hide/show a Group for each new page?

Need help App Organization
1

When you select the page is a native app, it tells you not to create new pages but instead to group “pages” that can be hidden/shown when needed.

So does that mean that I have to create an action for each time I need a new page?

And I have to add to hide all new Groups to each of those actions as well?

So for example so far I have 6 pages

On the “home” page, I have an action, on load to hide Groups 2-5

Then when they click a button to get to page 2, I have the action to hide page 1 and hide page 3-5.

Is this the correct way to go about this… or have I got this all wrong? It seems like it can get extremely tedious as my pages grow, or for things like multi-step forms.

2

You’ve got it right! It is more difficult but if you use a good naming scheme you’ll be just fine!

Here is an idea I’ve been working on that has all pages like you say but also optimized for desktop as their own page. I didn’t take the spa approach at first.

3

Thanks so much, glad to know I was setting that up right then. It’s definitely more tedious but still, has to be lots easier than coding which is why I’m here :wink: and thank you for sharing your project, that definitely helped visualize this better!

4

That’s it yes, but use custom states and conditionals to hide and show groups rather than using separate hide/show actions to hide and show every group every time a nav button is clicked.

1 Like