Enabling custom push server and transport
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
adding option for microG to talk to a custom push server (perhaps using a different transport if that will be more convenient) and forward information needed to proxy FCM notifications. This way people can use a freedom respecting push service and keeps existing apps functional, and app developers doesn't need to create two version of a app to use free push services, if the token they got is for google, they send the notif to google, otherwise to the push server directly, apps only need to understand FCM APIs.
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.
Research direction
The issue names no files or tests; start by mapping the existing FCM token and notification flow in GmsCore and identifying the push-server and transport boundaries. Define the custom-server behavior and token routing needed to preserve FCM-compatible app use, then verify the complete notification path for both Google and custom tokens.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, firebase, java
- Domain
- api, mobile, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100