> 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

Send timely alerts to your users, even when your app isn't open.

## 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 %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildnatively.com/natively-platform/features/notifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.