> For the complete documentation index, see [llms.txt](https://docs.buildnatively.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildnatively.com/natively-platform/features/notifications.md).

# Notifications

## What are Notifications?

Push Notifications let your app reach users on their lock screen or in their notification tray, whether the app is open, backgrounded, or fully closed. You can use them to bring users back after a delay, alert them to new activity, or deliver time-sensitive updates - order confirmations, chat messages, reminders, and more.

## Supported providers

**OneSignal** - the recommended option for most apps. Handles device registration, targeting, and delivery through a dashboard-driven setup, with minimal backend work required.

{% content-ref url="/pages/k9MsZswnHE6zIyEKzAn0" %}
[OneSignal - Push Notifications](/natively-platform/features/notifications/onesignal-push-notifications.md)
{% endcontent-ref %}

**Firebase (Advanced)** - for teams that need direct control over Firebase Cloud Messaging, or already have a Firebase-based backend and want to send notifications without going through OneSignal.

{% content-ref url="/pages/pMcjU4MdcfrIzYtmaYVN" %}
[Firebase - Push Notifications (Advanced)](/natively-platform/features/notifications/firebase-push-notifications-advanced.md)
{% endcontent-ref %}

{% hint style="info" %}
Most apps should use OneSignal. Reach for Firebase only if you have a specific reason to manage the messaging infrastructure yourself.
{% endhint %}