Before multipage apps I would create modules as pages and add a module to a container. I am creating a new app (multipage) and initially thought it would be the same. For the most part it seems to be an improvement.
However, a distinct difference is the versions. It seems, if I understand correctly, in a multipage app all pages have the same version. With my previous approach having modules as pages, I had versions per module or per page. This is useful for a variety of reasons, mainly to have a stable release of a set of modules while working on new modules and not having to push out everything at once.
Is there a way to have distinct versions per page or should I stick with my approach and continue using modules to have distinct versions and just embed them in their own page?
I would be curious to see how others do this.
1 Like
I faced a similar challenge and chose to continue developing my app using the same approach as you. Using modules helps me manage the versions of each section of my application.
Currently, it seems there isn't support for per-page version control. However, I have a strong feeling that the development team is working on this feature. The multi-page approach allows each page to function as a separate app, so the development is clearly moving in that direction.
+1 for this feature!
2 Likes
Thanks for sharing @Infinitybht. At least I'm not alone and on the right track. I'll stick with modules for the moment.
It would be fantastic if someone from the Retool team chimed in. 
1 Like
Hey @Shawn_Optipath,
Thanks for raising this feature as something multipage could support. your feedback helps us better understand how the product is currently being used by our builders. I've shared this feedback out with our team and will let you know if this is something we're considering for V2 of multipage.
2 Likes
Hey @AbbeyHernandez. That's fantastic news. Thank you.
1 Like