We had some hold-ups last year with keeping our vehicle production process in line with our software updates. That’s since been rectified, although we’re still working on improving the process to minimise that turnaround.
Indeed. The original Companion software was a decent first attempt at the functionality that’s been required over time, but because it was built up incrementally and without precedents it’s not structured amazingly for what it needs to do now, and is a bit unwieldy to work with/extend. The replacement takes our learnings from the first one to create a more modular and expandable structure, which should be easier to use on a variety of devices, and more robust when operating and granular when updating.
We’re definitely excited for the new structure and direction, particularly because it should be significantly easier for users and third-parties to develop their own extensions and additions, while also being easier for us to maintain and improve the core functionality 