Overall it was a great bike for less than 200 miles a day, as mentioned before the firmware update. Would have recommended it to anyone. And hardcore riders like Morgan and I could have struggled through the touring issues, as I did on the way up from LA and he did on his trip to San Simeon.
After the update though... I couldn't recommend it to anyone for rides over 5 miles. That's why we decided to make this a part 1. Hopefully, they get test automation and quality for their software releases fixed. It's not hard. I know because I was lead dev on a team that built a bionic eye. We integrated full hardware testing including button presses with robotics and software integration. from robots all the way through the code. It is doable and not hard if you know what you are doing. It would dramatically improve their customer experience and help their reliability issues. I would help them if they wanted. I have offered a number of times, but always been told that its not a real issue, and they have it under control. I first reported the first iteration of this bug in Europe when stranded charging at 2kw on an island north of Germany, south of Denmark in gale-force winds and rain. I was tied into the bike and saw it miscalculate the amp hours and it has been happening ever since. That was 2016 or 2017...
This is different though, now it has become a legitimate safety issue. That's why we showed it. Zero would do well to budget time and money to fix this problem as it is real, and dangerous. It makes an otherwise fun bike, unusable in many scenarios, Like Morgan getting stuck after riding 9.5 miles of a 27 mile ride. It was never dangerous before. This is new, and should never be allowed to happen again.
Just to be clear, if it gets fixed, it'll be a fun bike again. It's definitely king of the hill for wheelies!