Thanks for the response Liam. In the usage section, there is an example where the Menu component is used for navigation. So my understanding is, if there is a secondary navigation which shouldn’t be much prominent for the user, then it can be used in the menu.
One more question — Consider an app which has two different sections- like pre login and post login. Where pre login uses the menu component as there are no primary actions available at that scenario and post login has a primary navigation as shown below. Does having two different navigation types breaks the experience to the user?
Scenario: Pre-login has list of Stores added. User selects the store, logs in and then gets into the post login scenario. Post login has primary navigations such as Home, Apps and few others. Settings & Help are carried from the Pre-login screen to the navigation.
So i have used two different pattern based on the context in pre-login and post-login experience. Do you think this will confuse the user?

