I’m not a programmer, but from a customer service perspective, and from a safety perspective, anything that can be toggled on/off should be immediately available with voice commands. If they are put on a to-do list, Google won’t get to it. Volvo needs someone cracking the whip on Google and it’s (in my opinion) barely beta AAOS.
Don't agree that "anything" that can be toogled on/off should be available with a voice command, that opens the door to passengers being able to toggle on/off functions that should only be controlled by the driver, whether it's done as a "joke" or by accident.
Regarding cracking the whip on Google, I'm not sure who has more blame, Google if their AAOS has true shortcomings that are not being addressed, or the Volvo SW Development team for a lack of thorough verification and validation testing on their implementation and integration of AAOS. I'm leaning more towards the Volvo team, but not at all an easy task to engineer a whole new OS, UI, controls, etc. into a first generation EV. Most likely the SW team didn't have the necessary background/skillsets/manpower/etc for undertaking the task, and were signed up to an agressive schedule that management was not willing to move. This is a whole new paradigm for car companies, lessons learned for everyone (hopefully).