To clarify - The difference between Google Maps and Apple Maps:
If the phone is locked and navigation is in progress, on Apple, the active map shows in the lock screen. On Google, you would need to unlock the phone, and switch back to the Maps app.
Of course (and to be fair) if you don't lock the phone and leave the maps app focused, both Google and Apple will stay in view.
I've found that on longer drives where the maps app isn't needed, the phone will end up being locked/away, and when you do need a direction, that's when the API difference that I mentioned above clearly shows up.
Apple is definitely holding that API to themselves, with a side effect of making a more dangerous interaction (however un-ideal) for the user.
How you drive your car is your responsibility. Navigation or not. If you kill someone or get them handicapped it's on you. Be considerate. Safety over everything else man.
> I've definitely had several close calls in traffic, with faceId requiring me to type the password, switch back to the maps app etc, since google maps can't stay open while the phone is locked like apple maps.
You’ve had several close calls due to using your phone when you shouldn’t, putting others at risk. That sounds exactly like the definition of unsafe driving (and the strongest plausible interpretation of what you said).
> I think it's a pretty serious dark pattern when you consciously make an app unsafe for your user.
Nobody at Apple is making an app unsafe, but you are choosing to make the roads unsafe by using an app and interacting with your phone while driving.
It’s not against HN guidelines to call out incredibly unsafe behavior, even if it is the context for complaining about API differences.
I don't think anyone was debating that. It's more that apple is deliberately making it harder for Google to build apps that in turn make it easier for the customer to drive safely, for reasons of platform control and, ultimately, profit.
If the phone is locked and navigation is in progress, on Apple, the active map shows in the lock screen. On Google, you would need to unlock the phone, and switch back to the Maps app.
Of course (and to be fair) if you don't lock the phone and leave the maps app focused, both Google and Apple will stay in view.
I've found that on longer drives where the maps app isn't needed, the phone will end up being locked/away, and when you do need a direction, that's when the API difference that I mentioned above clearly shows up.
Apple is definitely holding that API to themselves, with a side effect of making a more dangerous interaction (however un-ideal) for the user.