Implement adaptive notification throttling based on user engagement

[RUKAYAT-CODER]

Background

undefined

Description

Reduce notification frequency if user hasn't engaged recently, increase when active.

Current Behavior

Fixed notification frequency

Expected Behavior

Adaptive based on engagement

Impact

📱 Better engagement
🔋 Reduced battery drain
👥 Less notification fatigue

Acceptance Criteria

• Track user engagement metrics
• Adjust notification frequency
• Test notification adaptation
• Monitor engagement impact
• Document engagement thresholds

Implementation Hints

undefined

Related Issues

• Offline Indicator Not Integrated #56
• README Missing Development Setup #118
• ci: add build verification for Android and iOS (#123) #135

[gloskull]

@gloskull has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hello,

I’m a developer with 4 years of hands-on experience working on production-grade systems and contributing to collaborative, open-source environments. I’ve carefully read through this issue and fully understand the problem it addresses, the expected outcomes, and the constraints outlined in the acceptance criteria.

I’m comfortable taking ownership from start to finish: reviewing the existing codebase and related context, designing a clean and maintainable solution, implementing it with attention to edge cases and correctness, and validating everything with appropriate tests and documentation where required. I place strong emphasis on clarity, reliability, and aligning closely with the project’s existing patterns and standards, so the final result is easy to review and integrate.

I’m confident I can handle this task efficiently and deliver a solid, well-structured solution that meets all the requirements without unnecessary complexity. I’m also open to feedback during implementation to ensure the outcome matches the maintainers’ expectations.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @gloskull to this issue.

[drips-wave]

Congratulations, @gloskull! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @gloskull: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @gloskull as part of the Stellar Wave Program's 5th Wave 🥳

😎 @gloskull: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.