Stacked-sheets vs. nav-stack-in-a-sheet for navigation hierarchies on top of a map

I couldn't help noticing that the Maps and Find My apps make extensive use of "sheets stacked on top of each other" to represent its navigation hierarchy, with a "new content comes in from the bottom" orientation instead of a navigation stack with "new content comes in from the right side" oriented transitions.

I'm interested in this topic because I have a similar navigation-hierarchy-over-a-map case in my app (with a custom map view though) and I'm torn back and forth between the approach of replicating the "stacked sheets" vs. putting a navigation stack in a sheet, esp. with the navstack approach being way more attainable with the iOS 26 glass design.

I couldn't find any guidance for this kind of UI in the Human Interface Guidelines; I'm leaning towards the navstack-approach for my app; but in terms of the behavior of the SwiftUI container views in this scenario it seems a little bit of an uphill path.

Any thoughts on what pattern should be preferred for presenting a deep navigational hierarchy on top of a map-like view?

The HIG contains some best practices when using modal presentations. Please review the documentation as a starting point.

It’s subjective to the purpose of your app, but from a user’s perspective, you might want to consider either a TabView that adapts into a sidebar layout on iPadOS, macOS, and tvOS, or a NavigationStack.

Stacked-sheets vs. nav-stack-in-a-sheet for navigation hierarchies on top of a map
 
 
Q