<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>odux</author><text>In this case, these are very complementary and can even be considered the same thing. the core Android auto idea is to give a driving interface with limited features, less distractions, large legible texts etc. It is by default displayed in the car displays but there can be cars which do not support this. For those situations Google had a solution to display the same interface on the phone. This was especially useful for people to get used to this technology before upgrading their car. Google probably decided that there are enough bee cars and enough after market units with this technology that they don&amp;#x27;t have to support this anymore. I think it is too early considering there are a lot of older cars on the road and there is a acute shortage of new cars.</text><parent_chain><item><author>jfoster</author><text>The fact that the situation exists where Google has two products that do the same thing and one of them has the same name as another of their products that does something different is just bad news overall. It&amp;#x27;s great that this specific instance will be resolved soon but are Google, as an organisation, learning any broader lessons at all?</text></item><item><author>Someone1234</author><text>Just in case some people are confused: There are two different things with the same name -&lt;p&gt;- Android Auto vehicle communication technology that mirrors your phone&amp;#x27;s screen to a vehicle&amp;#x27;s head unit.&lt;p&gt;- Android Auto phone app that displays the same interface on your phone&amp;#x27;s screen like a normal app (e.g. mount your phone up high and use directly, or use some other screen mirroring technology to send it to the head unit).&lt;p&gt;Only the SECOND is being discontinued, not the first. This is &lt;i&gt;still&lt;/i&gt; bad news for people who rely on it, but has no impact on Android Auto communications system.</text></item></parent_chain></comment><story><title>Google is shutting down its Android Auto mobile app in favor of Google Assistant</title><url>https://www.theverge.com/2021/8/20/22633755/google-android-auto-for-phone-screens-shutting-down-android-12-google-assistant-driving-mode</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>scld</author><text>The lesson, I guess, is that if you print money from some other dominant business unit, you don&amp;#x27;t have to have any other good ideas or execution.</text><parent_chain><item><author>jfoster</author><text>The fact that the situation exists where Google has two products that do the same thing and one of them has the same name as another of their products that does something different is just bad news overall. It&amp;#x27;s great that this specific instance will be resolved soon but are Google, as an organisation, learning any broader lessons at all?</text></item><item><author>Someone1234</author><text>Just in case some people are confused: There are two different things with the same name -&lt;p&gt;- Android Auto vehicle communication technology that mirrors your phone&amp;#x27;s screen to a vehicle&amp;#x27;s head unit.&lt;p&gt;- Android Auto phone app that displays the same interface on your phone&amp;#x27;s screen like a normal app (e.g. mount your phone up high and use directly, or use some other screen mirroring technology to send it to the head unit).&lt;p&gt;Only the SECOND is being discontinued, not the first. This is &lt;i&gt;still&lt;/i&gt; bad news for people who rely on it, but has no impact on Android Auto communications system.</text></item></parent_chain></comment><story><title>Google is shutting down its Android Auto mobile app in favor of Google Assistant</title><url>https://www.theverge.com/2021/8/20/22633755/google-android-auto-for-phone-screens-shutting-down-android-12-google-assistant-driving-mode</url></story>