Watch this video and then answer me these 3 questions:
Maybe room for improvement in the routing algorithm.
All great points.
I think the Blower is a good 1.0 effort, and it served me well this fall once I figured out all its quirks.
That said, I hope there is an emphasis placed on maturing the software during the off season. It will be nice to use the Blower with an improved 2.0 software next year.
I agree. 
@rgloverii
I hope I’m wrong, but I bet they will be busy with the snow blower.
And here I was hoping they would make improvements to the implements before the season they are needed. LOL (meaning I was optimistic the snowblower was the most mature in terms of development)
The S1 is definitely the most mature. Followed by the mower, the SAM, and then the blower. I too would really like to see active development on the not in use modules in the off season and only hot fixes for the in season modules. I mean ideally, it would be year round for all, but I don’t believe the team is large enough for that yet.
Hi Greg, thanks for sharing your feedback about the blower. Regarding the three issues you mentioned, I’ll need to discuss the first point with our product team and will make sure your idea is passed along to them. For the second and third points, I’ll also share them with the team for further improvement.
We know there’s still room to improve the blower’s software, and we’re actively working on making it better.
A possible problem with development in the off season, is design and development choices could be made that may not be the best choices. Feedback would be delayed and it could be more difficult to fix as compared to if it was discovered sooner.
I see advantages and disadvantages to both approaches.
I suspect they are doing it the way they are is because of resource constraints.
I feel like testing/validation can take place all through the year due to Yarbo being a product that is sold worldwide.
There is no need to wait until Spring/summer in the US to develop and test updates to the mower modules for example. I personally can’t test my mower in January, but there are plenty of other customers who could.
Same goes for the other modules. They just need to become PROactive about resolving the issues, versus REactive.
They have collected plenty of feedback on the various issues. Put them into a proper prioritized Jira Backlog and start working them in a logical order.
I was testing the mower in January last year. And still will. And having customers in Australia now in mowing season, they could have instant feedback. But I agree, it’s resource constraints.
They need regular hot fixes and release them often. One issue at a time. Customer choice on when to install (or not). Just like everything else I own, I’m in complete control of when and if.