No, this is simply the reality of software development. It takes time. It takes time to design, it takes time to write, and it takes time to test. Then you have to do N iteration loops of the above to perfect it.
Not necessarily relevant, though.
There are delays caused by software development issues and the difficult of planning/scheduling all that, and then there are "delays" due to misleading expectations caused by simply outrageous announcements that had nothing to do with software development planning/scheduling/implementation difficulties.
I guess a lot of us are arguing Tesla and the case of EAP is the latter, not the former.
Let's look at the known facts in two segments:
- The split from MobilEey was announced in June 2016
- AP2 and EAP were announced in October 2016, so a full quarter+ after MobilEye was announced to be gone
- AP2 hardware buidling started either in late September or early October depending on the source
This first set of facts clearly suggests Tesla knew MobilEye would not be a part of the AP2 hardware when EAP was announced and hardware was being built in October. So any suggestion MobilEye not being on board affected the EAP announcement is bollocks. Tesla had not announced EAP until October 2016, so they could have changed the announcement were it affected.
So, on to the second segment of facfts:
- In October 2016 Elon Musk, at an event, reportedly describes EAP as being beyond AP1 in December 2016.
- In October 2016, Tesla says the following standard features "will become available in December 2016": Automatic Emergency Braking, Front Collision Warning, Side Collision Warning, Auto High Beams...
- In October 2016, Tesla places this text for the rest of the year to the Design Studio where you select to buy EAP: "Enhanced Autopilot... four cameras... will match speed to traffic conditions, keep within a lane, automatically change lanes without requiring driver input, transition from one freeway to another, exit the freeway when your destination is near... is expected to complete validation and be rolled out to your vehicle... in December 2016"
- AP2 has not yet even reached AP1 parity in late May 2017, let alone is beyond AP1, or using four cameras for anything. All of the standard safety and automation features of AP1 cars have not yet been rolled out either in late May 2017.
What this second set of facts IMO comes down to is this: did Tesla know or should Tesla reasonably have known, in October 2016 (and later, since they did not change the texts on the website), saying those will or are expected to be available in December 2016 is misleading marketing. Is it plausible Tesla just had another six+ months of delays after December 2016, unforeseen to a reasonable expert at Tesla and everything instead looking like all this would actually be finished in December 2016...?
That is the question I believe the lawsuit will come down to. What did Tesla know in October 2016 (and in subsequent months as the texts on Design Studio/Tesla.com remained unchanged) and what they reasonably should have known and communicated about the status of EAP and the standard safety features. I believe there is a fairly high chance that Tesla did not set the December 2016 expectation based on software development estimations, but for unrelated business reasons, and that is the beef...
This case would look very different if Tesla would simply have stated, in October 2016, that EAP and the standard safety features will become available over the next 6-12 months.