# Platform guides

Step-by-step push setup for Swift, Kotlin, Jetpack Compose, React Native, Expo, Flutter and Capacitor apps.

## Pick your framework

- [Swift](/docs/push/recipes/swift) — native iOS, APNs through `UIApplicationDelegate`.
- [Kotlin](/docs/push/recipes/kotlin) — native Android, `FirebaseMessaging`.
- [Jetpack Compose](/docs/push/recipes/jetpack-compose) — Android, with the Android 13+ permission launcher.
- [React Native](/docs/push/recipes/react-native) — bare React Native, `@react-native-firebase/messaging`.
- [Expo](/docs/push/recipes/expo) — `expo-notifications` in a development build.
- [Flutter](/docs/push/recipes/flutter) — `firebase_messaging`.
- [Capacitor](/docs/push/recipes/capacitor) — `@capacitor/push-notifications`, in an Ionic or Capacitor app.
- [Web push](/docs/push/web-push) — the browser's `PushManager`.

## Every recipe

1. Get the platform token: the hex APNs token on iOS, the FCM token on Android, a `PushSubscription` on the web.
2. Register it with a stable `deviceId`. See [Device registration](/docs/push/registration).
3. Save the app's [push credentials](/docs/push/credentials) in Native Notify.
4. Send a [test push](/docs/push/verification), then an [audience](/docs/push/sending).

A Swift or Kotlin app runs from Xcode or Android Studio on a simulator, an emulator or a phone; nothing needs building first. iPhone sends need a paid Apple Developer Program membership and a registered Bundle ID, and Android sends need a Firebase project — [Push credentials](/docs/push/credentials) lists each step.

> **Android shows nothing on its own:**
>
> Android pushes are FCM data messages, so Kotlin, Jetpack Compose, React Native, Expo, Flutter and Capacitor apps show the notification themselves — each recipe shows how. A test send says `accepted` either way.

Any other framework — .NET, Unity, Kotlin Multiplatform, or a backend that holds device tokens — registers with the same JSON. See the [Quickstart](/docs/push/quickstart).
