I can think of one extremely annoying exception that was definitely an oversight, but generally these is a HIG that is associated with each of these. Not everything makes sense to be in a left-to-right stack. The windows that pop up from the bottom are supposed to have a different purpose (usually have a "Close" button) vs the nav stack that have a back button. 3rd party apps do their own thing.
I agree. I think what I'm getting at with that is less about how you structure your app, and more about my frustration that there is no universal way of going back. If the developer forgets to implement a back button, suddenly I can get stuck on a step and having to restart the app. In a non-iOS app UI (like desktop GTK, browsers, Windows UI or anything really) it's always really obvious that I can press the OS hotkey to go back, or press backspace/escape to get back to where I was before.
Very true. I moved from Android to iPhone few months ago and even through the current iPhone I use (iPhone 11) is smaller than my Android device (Samsung S20 Plus), I can't use it with one hand.
If you're using CarPlay, there is a phone call and you pick up, CarPlay changes the entire screen to the phone call (which is just the profile pic of the person you're talking to), even if you're using Maps or anything else.
Everything has a different way to be closed or go back to the previous screen. Sometimes you swipe up, sometimes to the left, sometimes there is a back arrow in the top left, sometimes there is a X in the top right. When to do what is often not clear, and there is no universal "go back" action that seems to work either.
Swapping application context goes by "last touched", and it's easy to get lost when swapping left/right and trying to look/copy/scroll from many apps.