Skip to content

Push notifications: real device push (FCM) to replace the WorkManager poll #44

Description

@Adron

Where this stands

Android currently delivers notifications by polling GET /api/notifications on a WorkManager
job
and raising local system-tray notifications (per-category channels, grouping, deep links,
a persisted last-seen marker, and the push channel of notification-preferences respected). That
shipped deliberately because there is no Firebase project.

It is a good fallback, but it is not parity: it costs battery, it is late by up to the poll
interval, and it stops when the OS decides it should.

What parity needs

POST /api/push/register and DELETE /api/push/unregister exist on the server and are not
used by the app
— without FCM there is no device token to register. The help centre's
notifications page currently documents push for iOS only, so the Android registration contract
should be confirmed with the owner as part of this work.

Blocked

Needs a Firebase project and google-services.json from the repo owner.

Done when

A notification raised server-side appears on the device without the app polling, routed to the
right channel and deep-linking to the right screen.


Filed from the parity review of feature/parity-wip @ 14d7795 against interlinedlist.com (OpenAPI /api/openapi.json, 233 paths) and the public help centre.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Big hole in a shipped featurearea:notificationsNotifications & pushblockedBlocked on something outside this repoepicA feature area tracked as a parent issueparityClosing a gap against interlinedlist.com

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions