Reducing MyGate Notification Fatigue to Recover Meaningful Engagement
Why MyGate residents mute the app and use it only for visitor approvals, with survey numbers behind it
✳The problem they went after
MyGate residents get alerts that do not concern them and a notice feed padded with advertisements, so they mute everything and stop opening the app for anything else. The survey backs it up: 33 percent had muted all notifications in the previous 30 days, 48 percent named ads mixed into society notices as the top irritant, and every interviewee opened the app only to approve visitors.
✳What they actually did
The submission names the behavioural loop, noise to distrust to mute to avoidance, and shows it collapsing engagement across payments, helpdesk, maintenance and community modules. A product carrying all of that ends up working as a doorbell. Sixteen solutions across four root causes produced three priorities: Noticeboard Segmentation splitting the feed into Official, Community and Marketplace tabs, a Simplified Home anchored on four core utility tiles, and Mute Guardrails that intercept a full-mute attempt and offer category-level controls instead.
✳What you can take from it
Worth stealing
- Noise to distrust to mute to avoidance loop named explicitly
- Survey data quantifies muting rate and ad irritation
- Mute Guardrails offer category controls instead of a block
- North star counts monthly non-approval feature use
Read this if
Facing notification fatigue or single-feature usage in a multi-module app
The transferable bitMute Guardrails is the sharp idea here: instead of fighting the mute, it treats the mute as a signal and offers the user a smaller cut. Worth studying too is how the north star is written, a monthly meaningful engagement rate targeting 10 percent improvement in three months, with engagement defined as using at least one non-approval feature.
✳The submission itself
Open the PDF →Reading on a phone? The embedded viewer is cramped — open the PDF in a new tab instead.
