40 lines
1.6 KiB
Markdown
40 lines
1.6 KiB
Markdown
# 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
|
|
|
|
Вывод: текущие проблемы в основном на стороне клиентской интеграции/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)
|
|
- Contacts endpoints:
|
|
- `GET /api/v1/users/contacts`
|
|
- `POST /api/v1/users/{user_id}/contacts`
|
|
- `POST /api/v1/users/contacts/by-email`
|
|
- `DELETE /api/v1/users/{user_id}/contacts`
|
|
- `GET /api/v1/notifications`
|
|
- `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)
|
|
- contacts API (`/users/contacts*`) + экран управления контактами
|