Add Support for Unified Push
Los mantenedores suelen responder en 7 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 15/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
- Lenguaje dominante
- Kotlin
- Estrellas
- 706
- Forks
- 73
- Merge medio
- 5 d 17 h
- PR fusionados (30 d)
- 8
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de FossifyOrg/Clock
-
feature request needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
FossifyOrg/Clock#504 · 1 comentario ·
Los mantenedores suelen responder en 7 días
-
Export stopwatch times as csvAbiertofeature request needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
FossifyOrg/Clock#492 ·
Los mantenedores suelen responder en 7 días
-
feature request needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
FossifyOrg/Clock#491 ·
Los mantenedores suelen responder en 7 días
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
FossifyOrg/Clock#448 · 2 comentarios · 1 reacción ·
Los mantenedores suelen responder en 7 días
-
feature request needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
FossifyOrg/Clock#446 ·
Los mantenedores suelen responder en 7 días
Todos los issues de FossifyOrg/Clock
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
utopia-rise/godot-jvm#1004 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
ankidroid/Anki-Android#22408 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 Menos de una hora Aptitud para principiantes 72/100
afarber/OpenMapView#22 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
nightscout/AndroidAPS#5245 ·
Los mantenedores suelen responder en 1 día