A lot of apps deviate constantly from the "blessed" patterns. The result is that as a user new to an app (or update), you have to click and gesture around to see what happens, and probably miss a lot of UI features because of that.
Most of the alternatives would be worse for either usability or maintenance, or both:
- don't track sleep in the Health app
- track sleep, don't provide alarms/notifications for the sleep/wake along with the schedule in the health app
- put almost all the UI for Health's sleep/wake in the Clock app instead
- provide almost identical UI in both the clock and health apps
I'm sure there are better implementations of the current UI tho'. E.G still link to the 2nd app, but have it _after_ the normal alarm clock in the vertical/reading order, and use better wording to explain the function and behaviour.
I wonder if they're trying to avoid having Clock ask for permission to read the HealthKit data, which presumably they would have to do in most other possible implementations.
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.
UI has no 'correct' approach, the only thing that matters is if people can happily use it.
Then I suppose it's the fault of the App Store reviewers. The point is that Android handles the activity stack on the OS level and has much stronger control over what a back button does.