The key point, really, is what are the core functions related to it being A CAR, not an entertainment system. Entertainment systems need to be replaced periodically as new data and programs become available, and are better located in the phone with as seamless a connection to the car as possible. Core functions that don't change often or are unsafe to change insecurely should be in the car's systems. Also, the car's systems need to keep working indefinitely even after updates are no longer available; phones are expected to be replaced every 2-3 (maybe 5 for Apple) years, so the phone OS and other apps are seldom updated for much longer than that on any particular hardware release.I've always thought that automakers would be at a disadvantage with any service people typically use on their phones. Not just maps, but also entertainment, home automation, messaging, etc. Google and Apple have billions of devices and users, and millions of app developers, to improve those services. A proprietary infotainment system by an automaker will always be playing catch up.
That's one reason I'm hesitant about a car based on Android Automotive (not Android Auto - it's the car's OS not a phone connection). Not only does that hand over a lot of data to Google that's hard to control, but it updates itself often. Sort of like Tesla by Google. But I don't see a commitment to a truly stable, secure OS that will run indefinitely without updates. I'm probably wrong, but I just have a bad feeling about it.