Notification API: In-app delivery only (no push/badge)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- api
Research direction
Start with the /apps/technical-guides/base-notifications guide and the /api/v1/notifications/send entry point described in the issue. Compare API notifications with the on-chain notification behavior, then verify that API notifications produce push, lock-screen, and badge alerts like on-chain notifications.
Written by the indexing model from the issue text.
Description
Description
Path: /apps/technical-guides/base-notifications
Problem
Notifications sent via /api/v1/notifications/send only show up in the in-app notification center. They don't trigger push notifications, lock screen alerts, or badge indicators.
This means users have no idea they received a notification unless they manually open the notifications panel.
What happens now
API notifications:
- Show in notification center ✓
- Push to lock screen ✗
- Badge on notification icon ✗
On-chain notifications (token transfers, etc.):
- Show in notification center ✓
- Push to lock screen ✓
- Badge on notification icon ✓
Why this matters
We tested with multiple users - none of them noticed the notifications until we told them to check. They just don't see them.
This defeats the purpose of notifications. Users need to be alerted about time-sensitive things like rewards expiring, events ending, or getting outbid. Right now the notification API is basically useless for user retention.
Suggested fix
Make API notifications behave the same as on-chain notifications - deliver them as actual push notifications that users will see.
- Dominant language
- JavaScript
- Stars
- 337
- Forks
- 798
- Avg merge
- 7h 24m
- Merged PRs (30d)
- 51
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from base/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·