Login and Navigation Infrastructure Windows App SDK (WinUI 3)

Hi everyone, I am trying to set up an infrastructure for a user login system and menu authorization. I am doing research to rewrite my current CRM project with Windows App SDK (WinUI 3). I want to use MVVM pattern and aim to keep my dependencies to a minimum. I have some experience with UWP and WPF in the past.

I am examining the "VanArsdel Inventory" UWP application from Microsoft sample projects. As far as I understand, they created the MVVM pattern themselves in this project. They did not use a framework. This is quite difficult for me to understand. I understand that there is an architecture that revolves between App.xaml, SplashScreen, ShellView, NavigationView pages. I understand that this is what should be in a CRM project.

If I come to what I want to ask; Is there a Microsoft best practice for Login and Navigation authorizations?

Start by reading the VanArsdel Inventory sample and the architecture points named in the issue: App.xaml, SplashScreen, ShellView, and NavigationView pages. The issue does not identify a target file, test, implementation scope, or acceptance criterion, so a contributor would first need clarification on the expected sample or documentation outcome.