The Courier Blog

Firebase CocoaPods support is ending. What happens to iOS push notifications?

Firebase is ending new Apple SDK releases to CocoaPods in October 2026. Your app will not break overnight, but your Firebase push notification stack can get stuck on old SDKs while APNs, iOS, Xcode, and Firebase keep changing.

Turn customer context into personalized messaging with AI

Build adaptive customer messaging with Courier Journeys. Use AI nodes to classify users, generate notification copy, enrich profiles, and route each workflow based on structured AI output.

Custom Environments: Ship Customer Messaging like you Ship Code

Courier workspaces now support custom environments. Each is fully isolated with its own templates, integrations, and logs. Match your messaging workflow to how you ship code.

AI Tools for Product Managers: The Modern PM Stack

The modern PM stack runs on AI at every step: Cursor and Claude Code for build, Pencil and Claude Design for prototyping, Courier for notifications and agent communication, Segment for routing product events and engagement data, PostHog for analytics and LLM evals, and a knowledge system like Notion for shared memory across humans and agents.

The AI Node in Journeys: Smarter Branching, Personalized Messages, and Live Enrichment

Courier Journeys now includes an AI node that you can drop into any customer journey. Use it to branch on logic too nuanced for if/then, generate message copy shaped by each user's context, enrich profiles with live data mid-flow, and batch activity into recurring digests. Existing deterministic journeys keep working. The AI node is additive, not a replacement, and it lets you unlock the kind of personalization that used to require a dedicated ML team. Here's what it does and how to use it.

Your Notification Center, Your Competitive Edge

The in-app inbox is the most valuable notification surface you own. Every other channel has a gatekeeper: push, email, and SMS all run through someone else's filters. The inbox is the one surface where you set the rules. Courier Inbox ships as a drop-in component backed by a hosted API that stores messages, syncs read state across devices in real time, and integrates with your other channels. SDKs for React, Web Components, React Native, Flutter, iOS, and Android. Install it with an AI coding agent or a few lines of code. Theme it, customize the renderers, or go fully headless.

Using Claude Design, Claude Code, and Courier AI to Create a Multichannel Onboarding Series in 30 Minutes

A walkthrough of building a four-part multichannel onboarding series (email, in-app inbox, mobile push, and Slack) in 30 minutes using Claude Code and Cowork to orchestrate, Claude Design to mock each channel, the courier-template-builder skill to translate mocks into Elemental JSON, the Courier MCP to publish templates, and the Courier CLI to test sends. Covers the strategy behind the sequence and recommendations for anyone doing the same.

Throttling notifications across product, transactional, and marketing streams

A notification throttle that drops every event over a limit works fine for marketing nurtures and fails for product notifications, because product events carry context users actually need. The fix is pairing throttling with auto-batch: overflow events feed a batch node that rolls them up into a single digest, optionally rewritten by an AI node that prioritizes and summarizes the contents. This guide covers per-stream throttle setups for transactional, product, and marketing flows, and how the Courier Journeys AI node and fetch-data node fit into the pattern.

5 Mistakes Teams Make Building Customer Journeys

Most journey problems don't announce themselves. They show up as rising unsubscribe rates, softer engagement, and a sense that messaging used to work better. This post breaks down five mistakes teams repeat when building customer journeys: shipping too many without coordination, building journeys with no exit criteria, treating channels as interchangeable, letting the org chart dictate the flow, and using time delays where event triggers belong. Each section names a specific fix you can apply before you ship the next sequence.