Skip to content

Bring the native notification centre in line with the web #71

Open

Description

@ricardovfreixo

I'm taking the README notification-centre roadmap item. I'll compare the current web notification UI and signed mobile API with the existing native screen, then bring supported notification types, presentation and interactions into parity using native EDGE components. Scope will follow the actual API contract; any missing backend capability will be reported rather than simulated. I'll keep the PR focused, add tests, run the suite/Pint, remove the completed README roadmap entry, and provide an Android device verification checklist plus screenshots/recording before marking ready. Checked open issues and PRs (including drafts) for notifications/activity/inbox/alerts; no competing notification-centre implementation found. Related scheduling and log-state PRs mention Notifications but do not claim this roadmap item.

Activity

  1. ricardovfreixo commented on Oct 22, 2026

    @ricardovfreixo
    ContributorAuthor

    Backend companions for the native notification-centre work:

    Full native preview parity needs these changes merged and deployed. The app handles missing fields safely. App implementation and README update are local and tested (1,271 passing tests); publishing the app PR is held for the author’s Android phone test. Its description will explicitly link both API dependencies, and the new API PR will be updated with the app PR URL.

  2. ricardovfreixo commented on Oct 23, 2026

    @ricardovfreixo
    ContributorAuthor

    Readiness recheck: the existing LOCAL Android test build is ready for a phone test, with 1,281 app tests passing (12,167 assertions), Pint clean, plus 6 core and 18 list contract tests. Fresh backend composer test passes 3,972 PHP tests at 100% coverage/type coverage. Independent Standards and Spec passes found no new functional bug.

    The combined app delivery is not yet clean-checkout testable: the Android Log reselect fix uses local NativePHP core/UI patches not present in either the current tracked refs or the newer SDK refs on main. All native source/tests must accompany the app through linked companion PRs and reproducible dependency refs; no hidden vendor-only setup. The app branch also needs rebasing onto current main (#73/#75/#76).

    Backend companions remain dev-null-sh/dev-null.sh#1004 (quote/image previews, marked ready for backend testing) and dev-null-sh/dev-null.sh#836 (rank details). Rich preview parity requires their deployment. Native Kotlin compilation/JVM execution, phone behavior and screenshots remain outstanding. The Latest-feed discrepancy still needs a post-refresh comparison; @mention completion is separately tracked in #78.

    No app PR has been published under the author’s phone-test hold. Its complete draft description now accounts for every introduced app/native component, all dependency and setup steps, mandatory 1G PHP build memory, test evidence and remaining gates. It must not be marked fully testable from a clean checkout until the native companions/refs are supplied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions