Feature description
Description:
Implement local update detection and notifications for third-party repositories by reusing the existing changelog parsing logic already present in the app.
Instead of relying on Firebase, the app can periodically check the "changelog.md" of user-added repositories locally, similar to how it already detects partial updates (e.g., identifying when only specific packages like YouTube require updates).
When a new version is detected, the app can trigger a local notification or update badge using the same existing notification strings (e.g., "New updates for patches are available – vX.X.X can now be installed"), without requiring any new UI or backend changes.
Firebase notifications would remain exclusive to official repositories.
Motivation
Motivation:
Currently, only official repositories receive update notifications via Firebase, while third-party repositories rely solely on manual checks.
However, the app already performs local changelog analysis to determine update relevance (e.g., per-package updates). Extending this logic to trigger local notifications would be a natural and lightweight improvement.
This approach:
- avoids additional server or Firebase usage
- reuses existing parsing and notification infrastructure
- maintains the current trust model (users already choose to add repositories)
- improves consistency between official and third-party sources
Although the original scope may not have been to support universal repository behavior, the current implementation is already moving in that direction. This feature would align with that evolution while keeping the implementation simple and efficient.
Acknowledgements
Feature description
Description:
Implement local update detection and notifications for third-party repositories by reusing the existing changelog parsing logic already present in the app.
Instead of relying on Firebase, the app can periodically check the "changelog.md" of user-added repositories locally, similar to how it already detects partial updates (e.g., identifying when only specific packages like YouTube require updates).
When a new version is detected, the app can trigger a local notification or update badge using the same existing notification strings (e.g., "New updates for patches are available – vX.X.X can now be installed"), without requiring any new UI or backend changes.
Firebase notifications would remain exclusive to official repositories.
Motivation
Motivation:
Currently, only official repositories receive update notifications via Firebase, while third-party repositories rely solely on manual checks.
However, the app already performs local changelog analysis to determine update relevance (e.g., per-package updates). Extending this logic to trigger local notifications would be a natural and lightweight improvement.
This approach:
Although the original scope may not have been to support universal repository behavior, the current implementation is already moving in that direction. This feature would align with that evolution while keeping the implementation simple and efficient.
Acknowledgements