It's the right thing to do, but it shows how broken "hyperlinking" is on iOS: after clicking the button, you get the health app on some specific screen. That screen has a "< Settings" button on the top left, which will obviously take you somewhere unrelated now. Assuming that we somehow recovered from clicking that, in the OS status bar there is a minuscule and ephemeral "< Clock" label, which _does_ take you back to the clock app, but disappears as soon as the user switches applications or to the home screen. However, the screen that took me there in the first place was some kind of "modal" which closed itself when the clock app went into background, so that's also broken.

I see little problem with most of that. Most of it follows the design language of the OS. I agree somewhat about the modal in Clock, but actually that one bothers me MUCH less than the endless 3rd party app use of pop-up web-views that really should just be a direct link to Safari (with the < Back_to_previous_app).

The < Back_to_previous_app is too small. It was clearly shoved into the OS long after the overall design was set. I feel it's correct that it doesn't take over the regular swipe-right-to-go-back navigation. Doing this better would have forced a significant redesign of the fundamental UI paradigms, IMO. That could have been very interesting.

I have not tried Android's event history thing. Whenever anyone hands me an Android to show me something, as soon as I hold it I manage to activate some "home" or "back" or "change app" feature that takes me away from the thing the other person was trying to show me. I've no idea what control I'm accidentally tapping, just by holding the device, but it's pretty consistent. So I'm not yet convinced of Android's improvements over iOS.