Obstacle Notice

The app now requires a 3 hour warning about no-go zones each time a task is started.

Did I miss something?

That trash needs to be hotfixed out of the app immediately.
Like, TOMORROW.

5 Likes

Some complainer put this in the Yarbo Users and Community FB Group…complete with a screenshot AND a support ticket, if you can believe that:

With the new App V3.15.3, this 5-second nag is EVERY TIME you click the yellow button to go to the Start / Preview screen for a Work Plan. It used to be once only.
Support ticket #95014.

3 Likes

Oh that guy complains all the time!

It is annoying, yes. But, that’s the point. People clearly aren’t paying attention to the warning. Maybe it should be a toggle off buried somewhere where it prompts you again to accept the risk.

You want to run that by the complainer, @Ken ? :joy:

2 Likes

Neither is the core. If you want something mutilated, draw a no-go around it.

3 Likes

I’m sorry for the inconvenience caused. The notice is intended as a precautionary measure to ensure the safe operation of Yarbo. I will share your feedback with our product team and we will reevaluate the format of the notice based on your input.

1 Like

@Yarbo-Forum Yes, I just got the response from Support…I mean “the complainer” did. Thanks for taking the feedback.

As with the “Next” option being hampered when creating No-go Zones, generally if the software is being hardened against missteps by users at the expense of knowledgeable users who are now annoyed or hindered, a better solution should be considered. The goals should be an improved user experience while lessening Support calls.

We all can probably take some homework to have a ponder at this. How can we decrease the Support burden through some other means than putting annoyances in the application? Are there design issues somewhere that would help streamline the UX while lessening errors? Documentation / education? More hardening of the product itself? What major “Top 10” problems are users, perhaps less experienced users, encountering, and how can they be mitigated?

The “easy Q&D fix” would be an Expert Mode, which I’d advocate over annoying experienced users, but that is only a bandage to shut up “complainers” like that guy – or girl, we don’t know – who posted about this on Facebook.

I’m rubbish at GUI – and the solution isn’t always nags added to the GUI anyway. Someone’s got some ideas, well, other than “Fix the d**n product!!!” :wink:

2 Likes

Yarbo appears to be experiencing some ongoing user experience challenges. It would be a major step forward to have someone dedicated to refining UX as part of the development process. Here are a few specific areas where improvements would go a long way:

  1. Obstacle Notice Behavior: The repeated obstacle notification with a countdown every time a job starts is excessive. It would be much more user-friendly to show this a few times and then allow users to dismiss it permanently—perhaps with a “Don’t show again” option.
  2. Map Zoom & Position Reset: The app resets the map view frequently, forcing the user to constantly zoom back in. This disrupts workflow and should ideally retain the user’s last position and zoom state.
  3. Preferences UI Inconsistencies: There are several alignment issues in the settings screens, and some buttons (like the “i” info icon on Edge Priority Setting) are unresponsive. These kinds of issues give the impression of unfinished UI.
  4. Repeated Popups: For example, when taking manual control, the “Stop charging?” confirmation often shows up twice—once before and once after a loading spinner. This feels like the spinner is timed rather than functionally linked to the confirmation action.
  5. Buried Common Settings: In the area settings, important options are hidden within the “Advanced” section, which needs to be expanded every time. These should be more easily accessible.
  6. Unnecessary Confirmation Dialogs: When exiting settings, a confirmation appears even if no changes were made. It would improve the experience to only show this when actual changes have occurred.

There are other examples, but these are some of the more persistent ones. Given the lead time between updates and the emphasis on testing, I’d encourage the team to consider tighter UX feedback loops to catch and refine these kinds of issues earlier.

4 Likes

Thank you for taking the time to share your thoughtful feedback. Your observations highlight several important areas for improvement, and we truly appreciate your effort in pointing them out. I’ve forwarded your message to the team responsible for app UX refinement so they can review and consider these suggestions in future updates. Your input is very valuable, and we’re grateful for your support in helping us enhance the Yarbo App experience.

2 Likes

@jeremyj114 - I think it was co-founder Ken K. who mentioned that Yarbo has hired a UX / GUI engineer to help with this stuff. GUI is hard, and it takes a special mindset to try to strike a good balance to make the most people happy.

2 Likes

@Ken oh, 100%. I have a UI/UX designer on my team, so I am aware of the challenges. With the scale that Yarbo is operating at, all interface design/qa should be filtered through them. I look forward to a much more polished product in the future, if what you say is true and they do in fact have a dedicated team member handing this task.

4 Likes