# Implement Some of the Feature Requests **URL:** \ **Category:** Suggestion and Feature Requests\ **Created:** [October 29, 2026, 2:41am UTC](https://forum.yarbo.com/t/implement-some-of-the-feature-requests/7879 "2026-10-29T02:41:13Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![jason.michas](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/jason.michas/32/6322_2.png) [@jason.michas](https://forum.yarbo.com/u/jason.michas)\ **Post date:** [October 29, 2026, 2:41am UTC](https://forum.yarbo.com/t/implement-some-of-the-feature-requests/7879/1 "2026-10-29T02:41:13Z")
I have had my Yarbo a year now and the whole time I have been on these forums watching and waiting. I think it is amazing that there is this whole list of stuff and it seems like zero gets done each release. I mean where are the new patterns for mowing? That request is like a year old at least. I even was involved in a thread where I suggested you guys make pattern development open source. Give us some API endpoints and let the community build “pattern builder tools”. Also, where are “sidewalks” for mowing aka one way dead ends? Another long time request and sorely needed for those of us with hilly terrain. How about smoothing the turning algorithm so it doesn’t stop, turn, drive, stop, turn, etc when it was recorded as a nice gentle arc using the app or controller? I feel like whatever you guys are working on you are missing the fact that there are two kinds of things you can do: quality of life fixes/features and low hanging fruit. A lot of the things you have are both but they never get done. ---
**Author:** ![Yarbo-Forum](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/yarbo-forum/32/126_2.png) [@Yarbo-Forum](https://forum.yarbo.com/u/Yarbo-Forum)\ **Post date:** [October 29, 2026, 9:33am UTC](https://forum.yarbo.com/t/implement-some-of-the-feature-requests/7879/2 "2026-10-29T09:33:11Z")
Hi there, I understand your frustration with so many long-standing feature requests that have yet to be addressed. We’ve recently improved our internal development process to better balance bug fixes, existing feature optimizations, and new feature development, while allocating our resources more effectively. Regarding the **one-way Dead End** feature, our product team has evaluated this request, but we currently don’t have plans to move forward with it. As for **new mowing patterns** , could you please share your ideas again? I’d be happy to bring them back to our product team for further consideration, including your suggestion about community-developed patterns. Regarding **smoother turning** , the current behavior is designed to maintain accurate path tracking and safe distances from boundaries and obstacles while keeping motion control stable. We understand that smoother, more continuous turns would improve the experience, especially when following curved paths, and I’ll share your feedback with our product team for future optimization. I know these requests have been raised for quite some time, and I appreciate you continuing to share your ideas and push for improvements. ---
**Author:** ![cobradunn](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/cobradunn/32/298_2.png) [@cobradunn](https://forum.yarbo.com/u/cobradunn)\ **Post date:** [October 29, 2026, 11:21am UTC](https://forum.yarbo.com/t/implement-some-of-the-feature-requests/7879/3 "2026-10-29T11:21:29Z")
Let me translate: Don’t expect much. Even the low hanging fruit is too much. I could post a list of 50 simple bugs sitting out there “to be fixed in future a update” Even critical life safety issues like fully documented and repeatable NGZ violations have gone unfixed for 6-9 months. That alone should tell you everything. Bet this beast is consuming a pile of development resources. ![image](https://canada1.discourse-cdn.com/flex007/uploads/yarbo/original/2X/0/0e73c81707911b371735b3bff69073066f537af3.jpeg) ---
**Author:** ![s.moz](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/s.moz/32/519_2.png) [@s.moz](https://forum.yarbo.com/u/s.moz)\ **Post date:** [October 29, 2026, 12:01pm UTC](https://forum.yarbo.com/t/implement-some-of-the-feature-requests/7879/4 "2026-10-29T12:01:22Z")
How have I not seen this? Was it at Equip Expo? Tell me more please! ---
**Author:** ![cobradunn](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/cobradunn/32/298_2.png) [@cobradunn](https://forum.yarbo.com/u/cobradunn)\ **Post date:** [October 29, 2026, 12:05pm UTC](https://forum.yarbo.com/t/implement-some-of-the-feature-requests/7879/5 "2026-10-29T12:05:43Z")
Yep. Pics on FB. I know nothing except what you see. ---
**Author:** ![s.moz](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/s.moz/32/519_2.png) [@s.moz](https://forum.yarbo.com/u/s.moz)\ **Post date:** [October 29, 2026, 12:10pm UTC](https://forum.yarbo.com/t/implement-some-of-the-feature-requests/7879/6 "2026-10-29T12:10:39Z")
I’ve been on the commercial side of things for 4 years now asking them to roll out a commercial product, so I’m ecstatic. I am going to remain this way until I hear the price 🤣 ---
**Author:** ![B-Mod](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/b-mod/32/292_2.png) [@B-Mod](https://forum.yarbo.com/u/B-Mod)\ **Post date:** [October 29, 2026, 12:52pm UTC](https://forum.yarbo.com/t/implement-some-of-the-feature-requests/7879/7 "2026-10-29T12:52:18Z")
I heard $30k plus. ---
**Author:** ![rcguymike](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/rcguymike/32/4166_2.png) [@rcguymike](https://forum.yarbo.com/u/rcguymike)\ **Post date:** [October 29, 2026, 3:49pm UTC](https://forum.yarbo.com/t/implement-some-of-the-feature-requests/7879/8 "2026-10-29T15:49:15Z")
My issue with asking for new mowing patterns is that the current are very finicky and could use help before going any further. Open sourcing might be an interesting idea but also with the turning issues you mentioned the turf damage issue needs to be top priority. [![Google Photos](https://canada1.discourse-cdn.com/flex007/uploads/yarbo/original/2X/7/7c7efaed63808c3dbba45f9261484273df61a9ba.png "Yarbo Adaptive pattern · Oct 1, 2025 – Oct 19, 2026 📸") ](https://photos.google.com/share/AF1QipOfOhjUb_oWK5mjLqsMRS2qqwwGz2nk1mlpShlmuMB2BGX7AOfiebhCVFUob9iKpw?key=OXAyS1F4anV2eWtnTDJzbnpDSDkyeDdXNXRYcDh3) [![Google Photos](https://canada1.discourse-cdn.com/flex007/uploads/yarbo/original/2X/d/d10176185c86d16979bbd847418d35cc548c616d.jpeg "Yarbo Turf wear · Jul 13 – Oct 24 📸") ](https://photos.google.com/share/AF1QipOZGgngv6ewdg8Wg1R2N9FnK-z07ywkkLa0zh_q_PCgSev9xyFkixCmX8PNVCv01A?key=aTA0dVpjeDBXZVdkUkpUT2p4VWRfdzZKNkV4M29R) ---
**Author:** ![jason.michas](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/jason.michas/32/6322_2.png) [@jason.michas](https://forum.yarbo.com/u/jason.michas)\ **Post date:** [October 29, 2026, 4:01pm UTC](https://forum.yarbo.com/t/implement-some-of-the-feature-requests/7879/9 "2026-10-29T16:01:58Z")
Imagine the damage when the beast goes rogue through a no go zone. 😛 ---
**Author:** ![cobradunn](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/cobradunn/32/298_2.png) [@cobradunn](https://forum.yarbo.com/u/cobradunn)\ **Post date:** [October 29, 2026, 4:04pm UTC](https://forum.yarbo.com/t/implement-some-of-the-feature-requests/7879/10 "2026-10-29T16:04:33Z")
After it goes through once, you can delete the NGZ. It won’t be needed anymore 🤣 ---
**Author:** ![jason.michas](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/jason.michas/32/6322_2.png) [@jason.michas](https://forum.yarbo.com/u/jason.michas)\ **Post date:** [October 29, 2026, 4:12pm UTC](https://forum.yarbo.com/t/implement-some-of-the-feature-requests/7879/11 "2026-10-29T16:12:32Z")
@Yarbo-Forum Ok, here was my basic idea but keep in mind I have no idea how the algorithms and code for mowing patterns or patterns for any attachment are designed. From a high level it is very simple, provide API endpoints to read, what I would design as, a definition file for a pattern. It would be some sort of structured file like JSON. Then provide an API endpoint to add a new pattern. Patterns could be private or they could be shared with the community so if someone makes for instance a “contoured parallel” pattern other users could pull it into their app/yarbo and select it for an area. We would probably need some way to update user created patterns as well so essentially full CRUD API endpoints and an update mechanism that notifies users a newer version of a custom pattern is available. Maybe a bug was fixed in it’s logic or something. I guarantee you if you took the time to extract the logic into something that could be exposed this way, we would have tools and patterns created inside a week. The community could take the burden of creating new stuff for specialized situations and you guys could do what you do. Obviously this could also apply to any attachment and also to the upcoming open platform stuff where we can create our own attachments. ---
**Author:** ![cobradunn](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/cobradunn/32/298_2.png) [@cobradunn](https://forum.yarbo.com/u/cobradunn)\ **Post date:** [October 29, 2026, 4:15pm UTC](https://forum.yarbo.com/t/implement-some-of-the-feature-requests/7879/12 "2026-10-29T16:15:00Z")
They can’t out of their own way currently. ---
**Author:** ![rcguymike](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/rcguymike/32/4166_2.png) [@rcguymike](https://forum.yarbo.com/u/rcguymike)\ **Post date:** [October 29, 2026, 9:34pm UTC](https://forum.yarbo.com/t/implement-some-of-the-feature-requests/7879/13 "2026-10-29T21:34:01Z")
Hmm, Gemini says it’s a bit more complicated than that and my head now hurts(been sick​😅)…I’ma go lay down​😅 > Not quite—and the giveaway is in how he describes sharing it: > > > _“…so if someone makes for instance a ‘contoured parallel’ pattern other users could pull it into their app/yarbo and select it for an area.”_ > > If he were talking about raw waypoints or mission paths, those are tied to **one specific piece of dirt**. An array of GPS coordinates generated for Yard A is completely useless to User B. > > For User B to download something from a community repo, open their Yarbo app, and tap **“Apply Pattern: Zamboni”** to their own uniquely shaped polygon, that file can’t just be static coordinates. It has to contain the **generative logic** —the algorithm that takes _any_ arbitrary boundary, cuts it into swaths, accounts for obstacle buffers, and calculates the turns. > > That is where his idea hits a architectural contradiction: > > ### 1. He describes a static file, but expects algorithmic behavior > > Jason calls it a _“definition file for a pattern… like JSON”_ and mentions _“fixing a bug in its logic.”_ > > JSON is just serialized data—key-value pairs, arrays, and numbers. It doesn’t execute logic. You can’t put a geometric polygon-slicing algorithm inside a JSON file unless: > > - Yarbo builds a full, proprietary declarative path-planning schema (a massive undertaking), or > - The “pattern” is actually executable code (like a Python or Lua script, or a WebAssembly binary) that Yarbo’s app or robot executes against the zone geometry. But executing arbitrary community code on an OEM robotics controller is a massive security and stability sandbox nightmare. > > ### 2. How Waypoint Ingestion _Could_ Make His Vision Work (Externalized) > > If the community were to build what Jason wants using **waypoint ingestion** , the architecture would have to live entirely **outside** the Yarbo app: > > ```auto > [Community Web App / QGIS / Fields2Cover] > │ > ├─ Imports Yarbo boundary (via API) > ├─ User chooses pattern (Zamboni, Contour, Custom) > ├─ Tool computes the math & generates yard-specific waypoints > │ > ▼ (API POST: raw waypoints) > [Yarbo Cloud / Core Unit] -> Executes run > > ``` > > In that model, the community repo shares open-source _path-planning tools or scripts_, not pattern files inside the Yarbo mobile app. The tool pulls your boundary, crunches the math on your PC or in a browser, and sends Yarbo a single “dumb” mission path to follow with onboard obstacle avoidance active. > > ### The Upshot > > Jason is asking for the simplicity of downloading a custom watch face or an .SVG vector, but expecting it to do the job of a spatial geometry engine inside Yarbo’s native UI. > > If Yarbo ever opens the ecosystem up to user pathing, raw waypoint/trajectory ingestion from an external tool is the only realistic way it happens—Yarbo will never let user-authored pathing algorithms run natively inside their proprietary mobile app stack.