benya/Messenger

Files

Codex 9296695ed5

Android CI / android (push) Failing after 4m47s

Details

Android Release / release (push) Has started running

Details

CI / test (push) Has been cancelled

Details

docs: document push token and firebase notification setup

2026-03-09 23:12:54 +03:00

1.6 KiB

Raw Blame History

Backend/Web/Android Parity Snapshot (2026-03-09)

1) Backend vs Web

Backend покрывает web-функционал почти полностью (~95-100%):

auth: login/refresh/me, register, verify-email, resend verification, request/reset password, sessions, 2FA
chats: list/detail, saved, discover, create/join/leave, members/bans, title/profile, pin/archive, invite-link, notifications, clear/delete
messages: list/send/edit/delete, status, search/thread, forward/bulk, reactions
media: upload-url, attachments create/list
realtime: websocket + typing/read/delivered/ping-pong
users: search/profile/blocked/contacts
search: global search
notifications: list + push-token register/unregister

Вывод: текущие проблемы в основном на стороне клиентской интеграции/UX, не backend-contract.

2) Web endpoints not yet fully used on Android

GET /api/v1/messages/{message_id}/thread (data layer wired, UI thread screen/jump usage pending)
GET /api/v1/notifications
POST /api/v1/notifications/push-token
DELETE /api/v1/notifications/push-token
POST /api/v1/auth/resend-verification

3) Practical status

Backend readiness vs Web: high
Android parity vs Web (feature-level): ~82-87%

4) Highest-priority Android parity step

Завершить следующий parity-блок:

GET /api/v1/messages/{message_id}/thread (UI usage)
notifications API + UI inbox flow
notifications delivery polish (channels/grouping/snooze/per-chat overrides parity with web prefs)