There’s tremendous potential to make this product truly exceptional—and most of that lies in the software. However, given the current release cadence, it’s possible we won’t see another update until the end of the growing season.
Maybe consider implementing one or two improvements at a time, testing them, and pushing updates more frequently. Many of us are working around a LOT of bugs and unfinished features, which adds unnecessary frustration.
This community has also provided a wealth of valuable feature suggestions—many of which appear relatively easy to implement. Acting on even a few of these would go a long way in reinforcing the value of the product and reassuring users that the significant investment is worth it.
Thank you for your continued support for Yarbo and for sharing your thoughtful suggestions.
We completely understand your desire for more frequent updates with smaller, incremental improvements. It’s a valid and valuable perspective. However, each software update must go through a full cycle — including development, internal testing, optimization, testing among PPP users, and further refinement. This process typically takes time and cannot be completed in a short window.
While we truly understand your expectations, we currently do not have plans to change the release cadence.
That said, we sincerely appreciate your trust in Yarbo and your belief in its potential. We’re committed to continuous improvement and will keep working hard to make Yarbo an exceptional product.
To be clear, this has nothing to do with the PPP members. We point out tons of issues every single release cycle, and only a fraction of them get fixed before being released to the public.
Speaking as a PPP member to anyone who wants to jump on the bandwagon of being a tester. It’s not all roses over here.
In order to test these updates, we are sending our robots out at least once a day if not more, recording, noting issues or successes. Dealing with the problems of out of bounds issues (more that just what the general community experiences), having our cores run into and over things we don’t want it to - planters, fences, flower beds, rocks, etc.
Then the downtime of when these unwanted experiences damage our robots and we wait for parts or replacements. Then there is the damage to our lawns from the constant runs.
So just keep all that in mind, as some will accuse you of being the shrill for the company, or a paid employee or paid content provider, or just as was pointed out here - not doing our job!
I happily offered to be a tester and got rejected. Based on what you all are saying, sounds like they’re getting enough of the bug reports, just can’t act on them fast enough.
like James has said the issues are getting found and reported. Yarbo fixes what they can before the release. Then continues to refine for the next update. They are trying to find the balance between release frequency and minimizing performance in user firmware updates.
They don’t have the balance. We are well into the mowing season and for those of us that have any complications in our yards, we have purchased a device that is not anywhere near the functionality the marketing info promised and frankly dangerous.
At this rate of release there will only be one (or remotely two) updates this season. And the current owners have what will soon be last year’s model with dev focused on the newest batch of yarbo pro customers to support.
