Mapped areas and work plans should be per-module versus universal for all modules

Suggestion and Feature Requests
1

TL;DR - Mapped areas and work plans should be per-module, or at least optionally per-module, versus “universal” areas and tasks that are selectable in the app no matter which module is connected to Yarbo.

Currently, work areas and work plans show up in the app and are available for use no matter which module is connected to the Yarbo Core. This causes unnecessary clutter and confusion within the app.

For example - When I am using the mower or blower modules, there is ZERO need for me to see the various work areas I created on my driveway and walkways for the snowblower module. And why am I able to select Snowblower work plans when I have the mower attached??? Now that I think about it, it would be amusing to see what Yarbo would even do if I selected a snowplowing task with the mower attached…

Anyway, from my perspective I can see cases where a mapped work area should be ‘universal’, such as a yard area that could be used with the mower, blower, or SAM. But in some cases, a work area (and work plans) should be specific to an individual module.

I propose the following elegant solution:

For work areas and work plans, add a check box to select which module(s) that area or task is applicable to. So for my front yard area, I could select SAM, blower, and mower, but deselect the snowblower. As a result, the map and plan lists would change in the app UI depending on which module is actually connected.

4 Likes
2

I also suggested having an option to assign a module (or modules) to a mapped item. Having one map handling the snowblower AND mower becomes unwieldy and causes problems with Pathways because over the overlaps you’ll undoubtedly have.

Yarbo was looking into implementing a filter to help with this (in addition to allowing Pathways to apply to whatever Area is above them, thus making Pathway behavior in overlaps a little more consistent).

I haven’t had an update on this in months, though, but I also hear from co-founder Ken K. that there are some big mapping/navigation changes coming that make this stuff moot, so maybe fixing what we have is lower priority? I don’t know.

3

Thank you for your detailed suggestion — it’s very well thought out and appreciated.

We’ve already considered the idea of having optional per-module mapped areas, and I’m happy to share that this is already on our development roadmap.

As for making work plans module-specific as well, that’s a great addition. I’ve passed your feedback along to our product team for further consideration.

Thanks again for helping us improve the user experience!

4 Likes