Best Practice for menu driven games/apps

Hey there,

I’m making a menu-driven app atm, and I’m trying to work out the best practices.

Atm I know of 3 ways

  1. To make the next window, I create a widget, add it to the viewport and then clear the child whenever I go back.

  2. I have a master blueprint for example for a house, when entering the house it loads every widget and then has kind of a numbered swapping system and when you leave the house all the children are cleared.

  3. MenuSwitcher could be a third option, but It requires a few things and doesn’t really suit what I need.

I think I’m leaning on number 2 as It means it can run the house instance, and as soon as I leave it Everything is gone. But while I’m in the house, If I’m flicking around rapidly It doesn’t have to load anything.

I’m curious what You guys use?

Thanks for reading.

ps. The level Blueprint would probably be the master of all of them.

update:
Ive changed my Mind Im going with the menu switcher.