<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Retention on App Coding</title>
    <link>https://appcoding.com/tags/retention/</link>
    <description>Recent content in Retention on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 07 Jan 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/retention/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Push Notifications Have a Spam Problem That Developers Built</title>
      <link>https://appcoding.com/2026/01/07/push-notifications-have-a-spam-problem-that-developers-built/</link>
      <pubDate>Wed, 07 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/2026/01/07/push-notifications-have-a-spam-problem-that-developers-built/</guid>
      <description>&lt;p&gt;Push notifications were introduced as a mechanism for delivering timely, relevant information to mobile users. They have become, in the hands of most apps, a mechanism for re-engaging users who have stopped using an app — delivered at volumes and frequencies that have trained users to disable notifications as a reflex rather than a deliberate choice.&lt;/p&gt;&#xA;&lt;p&gt;The data on notification effectiveness tells a story that most growth teams choose not to hear. Opt-in rates for push notifications have declined steadily as users have learned from experience what push permission grants apps permission to do. iOS&amp;rsquo;s explicit permission prompt — which apps must request before sending any notification — shows opt-in rates below 50 percent for most app categories. Users who do opt in disable notifications at rates that correlate directly with how many notifications an app sends, not with how relevant those notifications are.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
