engineer-push-notifications

Implement and troubleshoot Braze push notifications across iOS, Android, and Web.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/delta-and-beta/braze-agency --skill engineer-push-notifications
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineer-push-notifications
Source: https://github.com/delta-and-beta/braze-agency/tree/main/skills/engineer-push-notifications
Command: npx skills add https://github.com/delta-and-beta/braze-agency --skill engineer-push-notifications

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a concise, platform-focused reference for implementing and troubleshooting push notification delivery with Braze. It addresses gaps where notifications fail to reach devices, render rich media, execute background/silent work, or route deep links correctly across iOS, Android, and Web.

Core Features & Use Cases

  • Permissions & subscription states: how to manage OS-level permissions, Braze push subscription state, and foreground/background enablement.
  • Payload construction & rich media: guidance for mutable-content, content-available flags, attachment payloads, and Notification Service / Content extensions.
  • Silent/background delivery: patterns for background fetch, uninstall tracking, geofence sync, and limitations of silent pushes.
  • Deep linking & routing: custom schemes, Universal/App Links, AASA placement, and delegating link handling (e.g., Branch).
  • Testing & debugging: test sends, token registration checks, APNs/FCM configuration, and diagnostic logging strategies.
  • Platform-specific notes: iOS (Service/Content extensions, app groups, badge and sound rules), Android (FCM, channels, NotificationCompat), Web (service worker scope, VAPID, soft prompts).

Quick Start

Diagnose why an iOS rich push test failed and provide specific configuration and code fixes for APNs, the notification service/extension, and Braze SDK integration.

Frequently Asked Questions about engineer-push-notifications

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement rich push notifications with Braze across iOS and Android?

Deep linking for push notifications uses custom schemes, Universal Links, and App Links. Configure AASA placement for iOS and delegate link handling through Branch to route users to specific in-app content.

Why does my iOS rich push notification fail to display media?

Silent pushes execute background tasks using the content-available flag for background fetch, uninstall tracking, and geofence sync. They are limited by OS-level background execution limits and require proper subscription state management.

What is the best way to troubleshoot Braze push notification delivery failures?

Web push notifications require proper service worker scope configuration, VAPID keys for browser authentication, and soft prompts to request permissions. Ensure the Braze Web SDK is integrated correctly for reliable delivery.

Can I use silent pushes for background fetch and uninstall tracking?

Manage push notification permissions by requesting OS-level alerts, configuring Braze push subscription states, and handling foreground and background enablement. Web push requires soft prompts and VAPID configuration.

How do I set up deep linking for push notifications on iOS and Android?

Configure iOS push notifications by setting up Notification Service and Content extensions, enabling app groups for shared data, and applying badge and sound rules. Ensure APNs token handling and the mutable-content flag are correctly implemented.

Do I need Notification Service Extensions to display rich media in Braze push?

Android push notifications use FCM for delivery, require notification channels for categorization, and rely on NotificationCompat for rendering. Verify FCM token registration and Braze SDK integration for reliable delivery.