Well, it´s not a one shoe fits all type scenario for me and it all depends on the app, how big and complex it is etc.. When it comes to UI/UX, I try to follow Google´s material design guidelines as much as possible as I think they make sense in many ways (+ gives me an overarching "framework" of UI/UX to work after which makes UI/UX design whole of a lot easier).
I would typically lean towards doing something like this:
https://www.dropbox.com/s/1ym09g9nyd7xpmq/fpjournal.png?dl=0
In this app/scenario, I have a top bar with general system operations so things like profile, logout, search etc. and then I have a left menu with operations for all "modules" of the app (in this scenario, I have a 6 level menu i.e I can drill down 6 levels of operations (if needed) which makes the left menu able to hold A LOT of stuff). The left menu can also be minimized manually + automatically when needed (as in screenshot) or it could be expanded to give the user more context/info about left menu operations. I also have operations for each layout e.g on the journal layout (screenshot above), operations in the breadcrumbs or on the actual layout. In my experience, this "structure" of UI/UX things is the most versatile and works for very complex apps + the actual UX is good, easy to understand and use etc..