push-notify

Configure FCM and APNs push notifications across React Native, Flutter, and native mobile apps.

13|3|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill push-notify-heaptracetechnology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push-notify
Source: https://github.com/heaptracetechnology/heaptrace-skills/tree/main/mobile/push-notify
Command: npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill push-notify-heaptracetechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mobile apps struggle to deliver timely, reliable notifications across iOS and Android while handling user permissions, token lifecycle, and app-state differences. This skill provides a unified end-to-end implementation path for push notifications that works with FCM and APNs, including token management, permission strategies, and deep linking.

Core Features & Use Cases

  • End-to-end push setup: provider configuration for FCM/APNs across platforms.
  • Permission flows: user-friendly prompts with pre-permission strategy and provisional authorization.
  • Token lifecycle & multi-device support: registration, refresh, and per-device token management synced to backend.
  • Cross-state handling: foreground, background, and quit states with consistent UX and data synchronization.
  • Rich notifications & deep linking: support for images, actions, inline replies, channels/categories, and navigation via notification taps.
  • Debug & reliability: best practices for ensuring delivery, throttling, and silent pushes for data sync.

Quick Start

Install the push-notify skill into your mobile project and configure your FCM/APNs credentials, then run the app to verify permission prompts, token registration, and a basic notification flow.

Frequently Asked Questions about push-notify

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

FAQPage Schema
How do I set up cross-platform push notifications for React Native and Flutter?

Cross-platform push notifications require unified provider configuration for FCM and APNs. This enables end-to-end delivery across iOS and Android, handling provider setup, permission flows, and token management for React Native, Flutter, and native apps.

What is the best way to manage FCM and APNs token lifecycle across multiple devices?

Token lifecycle management involves syncing registration, refresh, and per-device token rotation to your backend. This ensures reliable multi-device token handling and delivery across FCM and APNs providers.

How do push notifications work when a mobile app is in background or quit states?

Push notifications handle foreground, background, and quit app states with consistent UX and data synchronization. This includes silent pushes for background data sync and cross-state handling to ensure reliable delivery.

Can I send rich notifications with images and deep linking using FCM and APNs?

Rich notifications support images, actions, inline replies, channels, and categories via FCM and APNs. Deep linking enables navigation through notification taps, using data and notification payloads for cross-platform delivery.

How do I handle user permission prompts for push notifications without losing users?

Permission flows use user-friendly prompts with pre-permission strategies and provisional authorization. This approach manages user permissions across iOS and Android to maximize opt-in rates for push notifications.

Why are my push notifications not being delivered to iOS and Android devices?

Push notification delivery failures often relate to token lifecycle issues, incorrect FCM/APNs provider configuration, or throttling. Debug and reliability best practices ensure delivery, proper throttling, and silent pushes for data sync.