On Android pressing "back" will take you to the last screen you were on; importantly this might be in the same app or a different one. It'll also do things like dismiss popups and hide the keyboard, since that's also moving back to a previous state.
The back-swipe on iOS is the equivalent of the Android "up" button, in that it's specific to the current app. It's also only going to work if the current app is deliberately supporting it, of course -- they might have their own UI chrome that doesn't respond to a swipe.
The other half of the "back" button behavior on iOS is that you can swipe left/right across the bottom of the screen to cycle between apps. (Or there's a special back-button in the toolbar if you've just followed a link that took you between apps.) So it does need more intentional-knowledge about what you mean to achieve.
But YMMV of course, this is going to be largely dependent on your own usage patterns, app choices, etc.
Honestly, having used both, I prefer the iOS separation of concerns. I've seen a lot of non-technical people get confused about what Android's "back" is going to do, so a button that'll do something different based on the context of how your reached the current screen apparently doesn't map well to many people's mental models of their phones.
Conventionally, most iOS apps seem to do it like Apple does with the native apps. E.g. when I click a link in an iMessage, it opens up the page in Safari and at the top left of the screen there is a little "< Messages" button that will take me back exactly where I was.
Honestly, it seems just like a Windows vs MacOS vs Linux thing. There are analogs for almost every behavior that is even a tiny bit popular, you just have to get comfortable with how to use it.
Swipe right from the left edge of the screen.