PushizoDocs
Getting started

React Native, Capacitor, Cordova, MAUI and Unity

Common setup order and platform-specific guides for the bridge SDKs that wrap the native Android/iOS SDKs.

The bridge SDKs (React Native/Expo, Capacitor, Cordova, .NET MAUI, Unity) wrap the native Android (com.pushizo:pushizo-android) and iOS (Pushizo) SDKs: queueing, sessions, delivery feedback, in-app rendering and trigger evaluation run on the native side; the surface is compatible with the legacy provider's v5. The common order is the same on every platform:

Connect the channels

Dashboard → Channels → Android Push (Firebase service account JSON) and iOS Push (.p8, Key ID, Team ID, Bundle ID). Both must become active via Verify.

Add the package

PlatformPackageNote
React Native / Expo@pushizo/react-nativeRN ≥ 0.74, New Architecture and the old architecture; Expo with development builds only (expo prebuild / EAS).
Capacitor (Ionic)@pushizo/capacitorDelegates to @pushizo/web on the web; pod install on iOS.
Cordovacordova-plugin-pushizocordova plugin add; native dependencies come via plugin.xml.
.NET MAUIPushizo.Mauinet9.0-android, net9.0-ios (PushizoIncludeIos=true).
Unitycom.pushizo.unity (UPM)https://github.com/pushizo/pushizo-unity.git#0.1.0; Android + iOS Build Support.

Native steps

  • Android: google-services.json → android/app/; the Google Services Gradle plugin; default notification icon via meta-data.
  • iOS: Push Notifications + Background Modes capabilities; optional Notification Service Extension (rich media, received).

Initialize

The same flow on every platform: initialize(appId) → login(externalId) → User.addTags → Notifications.requestPermission → Session.sendEvent. If you self-host, pass apiUrl.

Test push

Dashboard → Subscriptions → Test device → Send test push; received/opened should appear in Message Tracking.

Platform guides: React Native, Capacitor, Cordova, .NET MAUI, Unity.

On this page