With the recent upgrade in speed on Retool, it's so much easier to create great multi-page systems. Splitting up your apps allows you to reduce large loads to improve speed of queries, streamline maintenance and give a true admin portal feel to your apps.
We discuss when you should break up your application systems into separate pages (aka. separate Retool 'apps'), and how you should do this best. We also give some great UX/UI tricks to keep your application infrastructure performant and effective.
Top tips include:
Passing information between apps (local storage vs URL parameters)
Breadcrumbs for navigation
Organizing your apps and creating landing pages
Maintaining design consistency across header and sidebar navigation
Looking forward to your feedback and further ideas!
Hey! I guess I need a better understanding of your meaning of 'app' here. We suggest treating Retool 'apps' as pages, and combining them using URL params etc to create a multi-page setup.
Mostly, this entails using modules to create a consistent navigation set across each page so the transition between your 'apps' in Retool works more seamlessly and the user sees them more like pages than separate apps altogether. You can make it more advanced by passing information through the apps as users navigate so they can easily move around and the data they select persists. Does that help your question?
Example im building a hr management system i have right now 5 apps inside retool. Not using multipage app yet. Should i move all 5 app inside one multi page app?
Do you know if this feature will be available across all plans once the stable release is out? I'm really excited to use it and just want to confirm that it will be included in the "Team" plan that we have.
Hi,
I created my first multi-page app today. Is there a way to have event handler for the page load?
I have a global variable which stores several app states to for example enable/disable "next page" buttons. This works great, but if I have the URL to a certain page, I can just go to that page without having the correct state. My idea was to check the variable state on page load, and if it fails, goto the page that initializes the state.
