Viewing a single comment thread. View all comments

kleptokiller82 t1_jegdwyf wrote

Unfortunately you can’t force a company to use another companies technology (in this case android auto and CarPlay), only if that’s a genuine deal breaker for the majority will they adjust their strategy. If we’re talking about safety, better pay and conditions etc.. then you’re suggestions would absolutely help. The EU can do some things (such as the usb mandate for charging or all new cars required to have a SOS function to call police in the event of a crash) but these are open standards and not tied to a specific company.

0

ShuRugal t1_jegkytt wrote

>Unfortunately you can’t force a company to use another companies technology

Ignoring that we can do exactly that...

Something we can do without doing that is to require that if the car is sold with a physical capability, that capability must be enabled without additional fees being required.

Another option is to require that if the car is sold with a software integration feature, it must include integration with an open standard.

The third option, "force them to support someone else's software" is to mandate that if the car has any connectivity features, it must support connectivity with all devices having over a certain percentage of market share or raw number user base.

4

TheQuarantinian t1_jeh0tko wrote

IBM found out the hard way that exclusive tie-in was against the law. Once upon a time they tried to force only IBM brand punch cards to be used with their machines, but International Business Machines Corp. v. United States, 298 U.S. 131 (1936) put a stop to that.

So imagine that GM says "you can buy this car with remote start, but you can only use said feature if you also purchase a subscription to GMremote. And using DMCA protections we will block you from using an aftermarket remote starter.

That probably wouldn't fly.

1