<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>FCM on Nalar</title>
    <link>https://nalar.dev/tags/fcm/</link>
    <description>Recent content in FCM on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/fcm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Android Priority Notifications Are Not VIP Channels</title>
      <link>https://nalar.dev/android-priority-notifications-are-not-vip-channels/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/android-priority-notifications-are-not-vip-channels/</guid>
      <description>&lt;h1 id=&#34;android-priority-notifications-are-not-vip-channels&#34;&gt;Android Priority Notifications Are Not VIP Channels&lt;/h1&gt;&#xA;&lt;p&gt;A pager-style Android application can expose a button labeled &lt;strong&gt;VIP channel&lt;/strong&gt;, but Android does not turn that label into a private radio frequency, reserved cellular bearer, or guaranteed delivery path.&lt;/p&gt;&#xA;&lt;p&gt;What the application can build is a priority policy. A server can classify an event as urgent, request high-priority delivery from Firebase Cloud Messaging (FCM), and post the resulting notification to an Android notification channel with high importance. Those controls operate at different layers, and none of them alone provides pager-like delivery guarantees.&lt;/p&gt;</description>
    </item>
    <item>
      <title>FCM Is a Wake-Up Path, Not a Real-Time Transport</title>
      <link>https://nalar.dev/fcm-is-a-wake-up-path-not-a-real-time-transport/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/fcm-is-a-wake-up-path-not-a-real-time-transport/</guid>
      <description>&lt;h1 id=&#34;fcm-is-a-wake-up-path-not-a-real-time-transport&#34;&gt;FCM Is a Wake-Up Path, Not a Real-Time Transport&lt;/h1&gt;&#xA;&lt;p&gt;A mobile application can maintain a WebSocket while it is active and still need Firebase Cloud Messaging when the operating system suspends it. Those mechanisms solve different failure conditions.&lt;/p&gt;&#xA;&lt;p&gt;WebSocket, MQTT, and SignalR assume that a client can participate in a live communication session. FCM is useful precisely when that assumption no longer holds: the application may be backgrounded, its process may not be running, or its persistent connection may have disappeared.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
