Aeion BaaS + FCM (Firebase Cloud Messaging)
Configure FCM for Android (and optionally iOS + Web) push notifications in Aeion BaaS. Modern HTTP v1 API with service-account auth, Android + iOS + Web push via one endpoint, direct-send and campaign delivery. Aeion's push system wraps FCM alongside APNs and Web Push.
Setup — Firebase Side
- Create a Firebase project at
https://console.firebase.google.com
Setup — Aeion Side
```bash
Device Token Registration
Android apps register FCM tokens via the Firebase SDK, then send them to Aeion. Note: Aeion currently ships official BaaS client SDKs for Unity, Unreal, TypeScript, Python, Go, Rust, and Flutter — there's no dedicated native Android/Kotlin or Web/JS SDK, so AeionBaas.push.registerDevice(...) below is illustrative of the shape (call the Push API's register-token endpoint with the token and platform), not a real package you can import. Unity and Unreal apps should use Push.RegisterTokenAsync(...) from the official SDK; other native clients should call the token-registration REST endpoint directly.
Push Campaign Delivery via FCM
```typescript
Android-Specific Push Features
Android has richer notification surface than iOS.
FCM Web Push (Browsers)
FCM supports browser push via the Web Push standard.
Common Gotchas
- HTTP v1 vs Legacy API — FCM has two APIs: legacy (deprecated, Server Key auth) and HTTP v1 (modern, service-account auth). Aeion uses v1. If documentation tells you to use Server Key, that's the legacy path — don't use it.
FAQ
Aeion always routes iOS device tokens directly to APNs — there's no FCM-as-broker option for iOS in the current adapter.
Aeion is the alternative to Firebase's bundled services. Use FCM via Aeion for push; use Aeion Auth instead of Firebase Auth; use Aeion's Postgres + collections instead of Firestore. Mixing Firebase with Aeion is supported but adds operational complexity.
Free from Google for moderate volume. At high volume (millions of pushes/day), Google may impose quotas + require enterprise agreement. Aeion's push notifications are included in the flat $49/mo BaaS plan — no additional charge.
Yes. Aeion's send-to-player call resolves the platform per device-token + routes via the appropriate adapter. Your push CODE doesn't need to branch per platform.
Best-effort. FCM (like APNs) doesn't guarantee delivery. Aeion tracks "sent to FCM" status; "received on device" comes from app-side analytics.
Not currently — broadcast-style sends go through Aeion's own campaign system (server-side audience targeting + per-token delivery), not FCM's topic pub/sub.
Aeion's live-ops + remote-config layer supports per-cohort variants. Configure the variant lookup in your push template; the push system picks the variant per device.