Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Apple's risky bet on CarPlay

theturnsignalblog.com

Post reply on HN
Print view View original

461–470 of 537 posts

Re: Apple's risky bet on CarPlay

#461

Post by _yb2s »

4rt wrote: post #105
yabones wrote: post #34

There's an interesting gap when discussing carplay/aa. Cars from the 90s up until about 2013 can be easily fitted with a $500 head unit upgrade, and support carplay quite well. With the right tools, it can be done in about two hours right in your driveway. Cars from 2018 and up pretty universally support carplay, and it's generally quite well integrated into the car's infotainment system. But, between 2013 and 2017,…

Porsche has a reasonably priced upgrade path for their head units even in quite old cars which add Carplay. The value is obvious to them - it maintains a high resale value on older vehicles which maintains their higher current sale value. Something I found interesting when I was hacking my VW to add Carplay (without paying £300) was that a ton of manufacturers in the ~2016 era use the exact same head unit and OS but…

I think you’re finding “different” car manufacturers using that system because they’re all VW owned brands. You’ll find the rest of the parts on the car are mostly the same also. If you want to annoy an Audi owner, point out which VW model is 95 percent identical… in some cases like the Q7 vs VW Touareg, the VW model is even higher end and nicer.

Re: Apple's risky bet on CarPlay

#462

Post by _yb2s »

yabones wrote: post #34

There's an interesting gap when discussing carplay/aa. Cars from the 90s up until about 2013 can be easily fitted with a $500 head unit upgrade, and support carplay quite well. With the right tools, it can be done in about two hours right in your driveway. Cars from 2018 and up pretty universally support carplay, and it's generally quite well integrated into the car's infotainment system. But, between 2013 and 2017,…

Nowadays there are low cost Chinese kits that directly add AA/Carplay to most of those early integrated systems without even replacing the unit. They’ve reverse engineered the lcd and touch screen interfaces so they can hijack the screen.

Re: Apple's risky bet on CarPlay

#463

Post by throwaway11460 »

briandear wrote: post #447
heywire wrote: post #437

Earlier quoted context omitted.

I’m happy with the way Mazda has integrated CarPlay. No touch while moving, the navigation wheel moves a highlight around the screen to select buttons/links. I find it much less distracting.

Audi is similar. I think also Mercedes. It’s great.

The audi wheel with buttons around it is terrible. I have to look down to find the correct button, and then I need to look at the screen to wheel to the correct option.

Touchscreen is not better than physical buttons but at least I can still look forward while operating it.

This audi is the first time I actually started using Siri - and not because I like it.

Re: Apple's risky bet on CarPlay

#464

Post by EasyMark »

I don't understand why they never formed a committee and decide core basic features an OS should provide, set up an open spec API (a good one), and have that as a basis for android, ios, and mobile phones. Something like that could easily hold up for 20 years. Obviously we could put in climate controls, but all the cars should have the same basic "position" and "heirarchy tree" of where basic controls/settings are. Whenever I rent a car it's always a fkn hastle to find settings. That's all I ask :)

Re: Apple's risky bet on CarPlay

#465

Post by numpad0 »

eloisant wrote: post #400
numpad0 wrote: post #81

Earlier quoted context omitted.

I wonder how much of those frustrations has to do with Japanese market share of car industry; I think the touchscreen infotainment is not there because car manufacturers value it as integral and central part of car experience but simply because otherwise their product loses against one of Japanese brands. Japanese road network is a disorganized weighted node graph and absolutely not a grid, and a bulletproof navigati…

Honestly I would prefer to have a 2DIN hole where I can put whatever infotainment I want, instead of being stuck with whatever the car maker included, and that I can change without changing my car.

Yeah, it can't get pro-consumer and pro-right-to-repair than that. Disappointment with lackluster stock infotainment followed by disappointment in the move away from repairability felt a bit hypocritical to me knowing that world. 2DIN holes are fine!

Re: Apple's risky bet on CarPlay

#466

Post by shagie »

bunabhucan wrote: post #241
makeitdouble wrote: post #170

Earlier quoted context omitted.

Google Maps fails in subtle but weird and sometimes costly ways. On one side, it can't route through a bunch of valid paths. I first assumed it could be because of residents asking Google to cut traffic, but sometimes it's not even through residential areas. I see routes on the map that are avoided in favor of bigger loops, and when trying the shorter routes they're perfectly fine. Or perhaps it's the vehicle size an…

>avoided in favor of bigger loops At this point at google, I wouldn't be surprised if they were selling your route to advertizers to "optimize your driving experience."

It should not be a surprise at all.

https://web.archive.org/web/20230129231747/https://www.waze....

https://www.waze.com/ads/

Re: Apple's risky bet on CarPlay

#467

Post by thedrbrian »

heywire wrote: post #437
bambax wrote: post #435

Earlier quoted context omitted.

> why would car makers want to spend millions of dollars a year rolling their own infotainment system? This is addressed in the article: > There used to be a big difference in driving characteristics and technology between premium and budget brands. Compared to a Volkswagen, a BMW used to have a more powerful engine, better handling, and comfort features like seat-heating and cruise control. However, a Volkswagen Gol…

I’m happy with the way Mazda has integrated CarPlay. No touch while moving, the navigation wheel moves a highlight around the screen to select buttons/links. I find it much less distracting.

On the new mazda3 it’s no touch at all. They took it out completely

Re: Apple's risky bet on CarPlay

#468

Post by solardev »

Xixi wrote: post #401
numpad0 wrote: post #81

Earlier quoted context omitted.

I wonder how much of those frustrations has to do with Japanese market share of car industry; I think the touchscreen infotainment is not there because car manufacturers value it as integral and central part of car experience but simply because otherwise their product loses against one of Japanese brands. Japanese road network is a disorganized weighted node graph and absolutely not a grid, and a bulletproof navigati…

I'm not quite sure what you mean by saying that the Japanese road network is not a grid. In terms of actual layout, it's quite grid-like. I would even say it's usually much closer to a nicely laid-out grid than the mess any European city is. What Japan lacks are addresses that can be found easily without using a map. Apart from Kyoto, roads in Japanese cities don't have names (or number), so addresses within cities a…

That's really cool! I didn't realize that. Thanks for explaining.

Reminds me the Township & Range system in the US, which is still used in public land management: https://web.gccaz.edu/~lynrw95071/Township%20Range%20Explana...

Re: Apple's risky bet on CarPlay

#469

Post by prmoustache »

dzhiurgis wrote: post #438
prmoustache wrote: post #357

Earlier quoted context omitted.

Are you saying you can't listen to music in a Tesla without a subscription?

Bluetooth, radio, usb and using your phones hotspot is still an option (tho unrealistic given how shit iOS hotspot is)

ah right, that is just internet connection for anything else but maps

Re: Apple's risky bet on CarPlay

#470

Post by solardev »

makeitdouble wrote: post #265
pr337h4m wrote: post #225

Earlier quoted context omitted.

Why not use plus codes? They're well-integrated into Google Maps: https://maps.google.com/pluscodes/

TIL. The weird part is Maps will accept them for search, but not display the plus code except when looking at POI (randomly selecting a point on the map doesn't show it for me, I only could get that from the /pluscodes/ map) This seems genuinely useful, but as usual we're having the chicken and egg problem to get it adopted ?

In mobile at least, you can touch and hold to make a red temporary POI that will show you the plus code.

But yeah, nobody uses it in the real World. If I need to share a point with someone else I'll just send them the Google Maps share URL instead, which has its own shortcode

Post reply on HN