I think the downside of it, from a manufacturer's point of view, is that there's probably a fair amount of coding (and then debugging) to incorporate it into your infotainment ecosystem. Then you have this very important bit of code that has to interface with this other device who's operating system configurations are myriad and always changing. There are going to be some patches/updates to your car's software that are going to be driven by changes to AA and ACP. Now your software ecosystem is not all your own and that can be disconcerting. Some car manufacturer's may also see this as commoditizing, a major aspect of their car. There's better software available on phones for everything a car manufacturer's infotainment system does, except for controlling the intrinsic hardware in the car itself. So they lose some control over what they might see as their ability to differentiate themselves from other cars.
In fact at this point I think Toyota flat refuses to include AA or ACP and are very blunt about telling their customers so.
Not that I think any of this is really valid, but playing devils' advocate.
In fact at this point I think Toyota flat refuses to include AA or ACP and are very blunt about telling their customers so.
Not that I think any of this is really valid, but playing devils' advocate.