maui-shell-navigation

Use Shell.Current.GoToAsync with a route string, always awaiting the call. Use absolute routes prefixed with // for hierarchy locations, relative routes for registered detail pages, and .. to go back one level.

Pass parameters via query strings like animaldetails?id=5, received through the QueryProperty attribute or IQueryAttributable on the ViewModel. For complex objects, use ShellNavigationQueryParameters to pass objects without string serialization.

Avoid Shell navigation for deep linking from external URLs, which uses app links instead, and for apps built on NavigationPage without Shell, which use a different navigation API. Data binding and dependency injection are handled by separate concerns.

Silent failures occur when relative routes are not registered with Routing.RegisterRoute, absolute paths do not match the full visual hierarchy, or the call is not awaited. Duplicate route names also throw ArgumentException at registration.

Override OnNavigating in AppShell and call args.GetDeferral() for async checks. Show a confirmation dialog, call args.Cancel() if the user declines, then call deferral.Complete() to finish.