Add Support for Unified Push
维护者通常 7 天内回复
还没有人认领这个 Issue。
评估
调研方向
The payload names no files, tests or entry points, so start by reading CONTRIBUTING.md and the repository's notification-related code. This is design work: it needs a maintainer decision on which UnifiedPush distributor and library to use and how delivery fits the app. Done means an agreed design and an implementation that receives push messages through a UnifiedPush distributor such as Sunup, with the issue thread settled first.
由索引模型根据 Issue 内容生成。
描述
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
It would be great if you could add support for Unified Push applications, such as Sunup, to enable notification delivery. Thank you! ❤️
Why do you want this feature?
It would improve ease of use for users who wish to avoid Google Play Services and bypass the proprietary Google FCM notification system
Additionally, implementing Unified Push would prevent multiple apps from individually consuming phone resources. Unlike regular polling, which requires each app to wake up the CPU frequently, Unified Push allows apps to share a single, efficient connection for notifications, significantly improving battery life
Additional information
No response
- 主要语言
- Kotlin
- 星标
- 706
- 派生
- 73
- 平均合并
- 5 天 17 小时
- 30 天内合并 PR
- 8
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
FossifyOrg/Clock 的其他 Issue
-
feature request needs triage
难度 2/5 1-3 小时 新手友好度 75/100
FossifyOrg/Clock#504 · 1 条评论 ·
维护者通常 7 天内回复
-
feature request needs triage
难度 2/5 1-3 小时 新手友好度 75/100
FossifyOrg/Clock#492 ·
维护者通常 7 天内回复
-
feature request needs triage
难度 2/5 1-3 小时 新手友好度 70/100
FossifyOrg/Clock#491 ·
维护者通常 7 天内回复
-
bug needs triage
难度 2/5 1-3 小时 新手友好度 72/100
FossifyOrg/Clock#448 · 2 条评论 · 1 个 reaction ·
维护者通常 7 天内回复
-
feature request needs triage
难度 2/5 1-3 小时 新手友好度 72/100
FossifyOrg/Clock#446 ·
维护者通常 7 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
rustyrazorblade/easy-db-lab#1017 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
-
难度 2/5 1-3 小时 新手友好度 72/100
callstack/react-native-brownfield#492 · 1 条评论 ·
维护者通常 4 天内回复
-
fix: retain the best partial noise-correction solution可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
world-federation-of-advertisers/cross-media-measurement#4653 ·
维护者通常 1 天内回复