# Push notifications

**URL:** <https://forum.yarbo.com/t/push-notifications/3232>\
**Category:** Suggestion and Feature Requests\
**Created:** [July 28, 2025, 1:37am UTC](https://forum.yarbo.com/t/push-notifications/3232 "2025-07-28T01:37:17Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![joe](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/joe/32/3813_2.png) [@joe](https://forum.yarbo.com/u/joe)\
**Post date:** [July 28, 2025, 1:37am UTC](https://forum.yarbo.com/t/push-notifications/3232/1 "2025-07-28T01:37:17Z")

</div>

I know this has been an active discussion topic. May I suggest that you prioritize a push notification for track slippage? Otherwise I need to monitor yarbo continuously to make sure its not slipping.

---

<div class="post-metadata">

**Author:** ![Micke](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/micke/32/257_2.png) [@Micke](https://forum.yarbo.com/u/Micke)\
**Post date:** [July 28, 2025, 1:45am UTC](https://forum.yarbo.com/t/push-notifications/3232/2 "2025-07-28T01:45:06Z")

</div>

See my post earlier today…

---

<div class="post-metadata">

**Author:** ![bryan.wheeler](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/bryan.wheeler/32/215_2.png) [@bryan.wheeler](https://forum.yarbo.com/u/bryan.wheeler)\
**Post date:** [July 28, 2025, 2:31am UTC](https://forum.yarbo.com/t/push-notifications/3232/3 "2025-07-28T02:31:45Z")

</div>

They do support push notifications for this. However, it doesn’t always work.

---

<div class="post-metadata">

**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:** [July 28, 2025, 3:05am UTC](https://forum.yarbo.com/t/push-notifications/3232/4 "2025-07-28T03:05:17Z")

</div>

Thank you for sharing your experience with us. I completely understand how important this notification would be, and I’ve already passed your feedback along to our product team for further consideration.

---

<div class="post-metadata">

**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:** [July 28, 2025, 1:07pm UTC](https://forum.yarbo.com/t/push-notifications/3232/5 "2025-07-28T13:07:25Z")

</div>

I have never gotten a single notification on my iPhone or Android tablet other than Work Plan Completed - the least useful of all the potential messages. What notifications are you getting?

---

<div class="post-metadata">

**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:** [July 28, 2025, 2:35pm UTC](https://forum.yarbo.com/t/push-notifications/3232/6 "2025-07-28T14:35:20Z")

</div>

Wish I understood why these super simple issues are not getting fixed. There’s very little risk of breaking anything else by correcting them.

---

<div class="post-metadata">

**Author:** ![bryan.wheeler](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/bryan.wheeler/32/215_2.png) [@bryan.wheeler](https://forum.yarbo.com/u/bryan.wheeler)\
**Post date:** [July 28, 2025, 3:39pm UTC](https://forum.yarbo.com/t/push-notifications/3232/7 "2025-07-28T15:39:55Z")

</div>

I have received track slippage (sometimes) out of boundary, geofence, and a couple of others I cannot recall. I don’t always get the work plan completed either. But I am often on beta firmwares and apps and I think that might be a factor sometimes (why I don’t get them). Not entirely sure.

---

<div class="post-metadata">

**Author:** ![Micke](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/micke/32/257_2.png) [@Micke](https://forum.yarbo.com/u/Micke)\
**Post date:** [July 28, 2025, 4:55pm UTC](https://forum.yarbo.com/t/push-notifications/3232/8 "2025-07-28T16:55:34Z")

</div>

They might wish to consider a dev freeze for a a week and dedicate the team only at fixing the minor bugs and missing features. My bet is that they never get fixed or addressed because everyone is focussed on big developments and improvements, so the small fixes never reach the priority level to get assigned. Sometimes you have to pick a few of them, else they will never get fixed…

Notifications, scheduling issues, UI issues raised here and there, no compatibility with password managers (really?) those quirks make the experience less enjoyable and each of them could take only a few hours (or even minutes in some instances).

Bluetooth conflicts, RTK issues, computer vision, fusion navigation, all important stuff that needs to improve in order to remain in the competition, but so much more complex…

---

<div class="post-metadata">

**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:** [July 28, 2025, 5:00pm UTC](https://forum.yarbo.com/t/push-notifications/3232/9 "2025-07-28T17:00:39Z")

</div>

The release pace and number of changes in each make me wonder how many people are actually working on it.

---

<div class="post-metadata">

**Author:** ![steve](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/steve/32/816_2.png) [@steve](https://forum.yarbo.com/u/steve)\
**Post date:** [August 5, 2025, 2:22am UTC](https://forum.yarbo.com/t/push-notifications/3232/10 "2025-08-05T02:22:47Z")

</div>

> [@cobradunn](#):
>
> make me wonder how many people are actually working on it

That number is probably divided by four, since they probably have to repeat the work and regressions for each module, separately.

---

<div class="post-metadata">

**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:** [August 5, 2025, 12:09pm UTC](https://forum.yarbo.com/t/push-notifications/3232/11 "2025-08-05T12:09:07Z")

</div>

Ah, yes. Why fix it once when you can do it three times 🙂

---

<div class="post-metadata">

**Author:** ![ken.w.gregory](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/ken.w.gregory/32/922_2.png) [@ken.w.gregory](https://forum.yarbo.com/u/ken.w.gregory)\
**Post date:** [August 5, 2025, 12:33pm UTC](https://forum.yarbo.com/t/push-notifications/3232/12 "2025-08-05T12:33:25Z")

</div>

Push notification work for out of bounds.

Yarbo spent the night over the grassy knoll when GPS can be less than adequate.

 ![IMG_3460](https://canada1.discourse-cdn.com/flex007/uploads/yarbo/original/2X/b/bba243b7fc9270e66122b59c8c9cb37b31c962c7.jpeg)

---

<div class="post-metadata">

**Author:** ![bryan.wheeler](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/bryan.wheeler/32/215_2.png) [@bryan.wheeler](https://forum.yarbo.com/u/bryan.wheeler)\
**Post date:** [August 5, 2025, 5:05pm UTC](https://forum.yarbo.com/t/push-notifications/3232/13 "2025-08-05T17:05:08Z")

</div>

Those and the geofence alerts are spammy. And I’m ok with that.

---

<div class="post-metadata">

**Author:** ![ken.w.gregory](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/ken.w.gregory/32/922_2.png) [@ken.w.gregory](https://forum.yarbo.com/u/ken.w.gregory)\
**Post date:** [August 5, 2025, 5:41pm UTC](https://forum.yarbo.com/t/push-notifications/3232/14 "2025-08-05T17:41:04Z")

</div>

Kind of scary waking up to a plethora of out of bounds only to find Yarbo sitting in bounds, right on the plan line with good GPS.

It’s been said before, but it should auto resume in my opinion.

---

<div class="post-metadata">

**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:** [August 27, 2025, 12:28am UTC](https://forum.yarbo.com/t/push-notifications/3232/15 "2025-08-27T00:28:07Z")

</div>

Here we sit yet another month later and no BASIC notifications of stoppages. How can anyone trust this to run unmonitored. WE NEED TO KNOW IF A PLAN STOPPED AND THE REASON! The lack of updates to correct downright basic functionality is very disturbing.
