FAQ

Frequently asked questions

Short answers about what the app does, what it does not do, and how it protects data.

Does Firebase Notifier replace Firebase Console?

No. The app is for composing, testing, validating, sending, and reusing FCM notifications. It does not create Firebase projects or replace Firebase Console analytics and campaigns.

Why does the app use Google Sign-In?

Google Sign-In lists the Firebase projects available to the connected account and sends notifications with that account's permissions through FCM HTTP v1.

Can I validate without delivering a notification?

Yes. The app supports FCM validate_only so a payload can be checked without delivery.

Are templates available on the free tier?

Creating and viewing can be free. Advanced actions such as reusing history, sending from templates, Drive sync, and larger scheduler capacity are intended for Pro or Max.

Does scheduling work without a backend?

Schedules can be prepared locally, but reliable timed execution requires a backend. This repo includes a single-instance Docker backend for local testing and a first VPS deployment.

Does Google Drive execute scheduled notifications?

No. Drive sync stores app data in appDataFolder. Scheduled execution belongs to the backend.

Where are Firebase secrets stored?

They must not be stored in Google Drive. For real server delivery, a service account should be mounted as a VPS backend secret.

Which platforms are planned?

Firebase Notifier targets iPhone, iPad, and macOS with the same functional rules and adaptive interfaces.