-
Notifications
You must be signed in to change notification settings - Fork 82
Notifications Setup
Operational guide for the mobile push stack. Architecture context: Realtime and Notifications.
Canonical source:
docs/guide/NOTIFICATION_SETUP_GUIDE.md— this page summarizes it; the repo guide has the exact setup steps and file references.
- Firebase Cloud Messaging (FCM) for delivery + Notifee for local presentation/handling on the device.
- A
yc://deep-link scheme so a tapped notification routes to the right screen. - A defined Android notification channel id for categorized delivery.
- The libraries involved and how they fit together.
- Key entry-point files in
apps/mobileAppYCthat wire up registration, foreground/background handling, and deep-link routing. - Step-by-step setup (permissions, channel creation, token registration).
Push payloads originate from the backend's NotificationService, invoked directly by the mutation flows (there is no event bus today — the org-event bus in Realtime and Notifications is an unimplemented design). Heavier async sends (reminders, batched notifications) run on BullMQ workers — see Backend: Realtime, Chat, Jobs.
Home · Architecture · ADRs · Plans · Roadmap · Contributing · Main repo · DeepWiki · Discord
Yosemite Crew is a product of DuneXploration UG (haftungsbeschränkt). This wiki mirrors the repository; where a page and the repo disagree, the repo wins. See the Wiki Style Guide.
Product & Domain
Architecture
Applications
- Backend — Overview
- Frontend / PIMS Web — Overview
- Mobile — Overview
- Desktop PIMS Shell
- Developer Portal
- SuperAdmin
Design & Accessibility
Engineering Handbook
Decisions (ADRs)
Design Docs & Plans
Meta
Canonical code & docs: main repo · Auto-generated companion: DeepWiki