- Added explicit coverage for activeDid-aware retry policy enhancements
- Specified Android DailyNotificationFetchWorker.java modifications for activeDid change detection
- Specified web callback-registry.ts enhancements for authentication refresh
- Added platform policy unification (android 1min→1hour vs web 1sec→1min standardization)
- Added integration with existing circuit breaker and error handling systems
This addresses the gap where scheduled event retry enhancements were only
mentioned at high level but lacked specific implementation steps.
- Added Current Implementation Baseline section documenting existing functionality
- Updated authentication examples to enhance existing DailyNotificationETagManager.java
- Modified HTTP request implementation to extend existing DailyNotificationFetcher.java
- Updated plugin interface to extend current DailyNotificationPlugin rather than replace
- Corrected implementation phases to build upon existing infrastructure:
* Phase 1: Extend core infrastructure (not rebuild)
* Phase 2: Add activeDid integration to existing methods
* Phase 3: Enhance existing background integration
* Phase 4: Add TimeSafari-specific features
- Updated Android examples to show enhancement of existing SQLite + SharedPreferences
- Updated Web examples to enhance existing IndexedDB (no host delegation initially)
- Changed status from 'implementation plan' to 'enhancement plan for existing implementation'
- Aligned dependencies with existing plugin infrastructure rather than new requirements
The plan now accurately reflects building upon our working plugin instead of
rebuilding from scratch, providing a realistic enhancement roadmap.
- Consolidated DATABASE_ACCESS_CLARIFICATION.md content into main plan
- Consolidated ACTIVE_DID_CHANGE_REQUIREMENTS.md content into main plan
- Consolidated TIMESAFARI_INTEGRATION_ANALYSIS.md content into main plan
- Enhanced main document with Option A architecture overview
- Added comprehensive TimeSafari integration patterns section
- Added critical requirement section for activeDid change detection
- Added event-based solution implementation details
- Updated README.md to reference single consolidated document
- Eliminated unnecessary document proliferation as requested
The BACKGROUND_DATA_FETCHING_PLAN.md now serves as the single source of truth
for all implementation guidance, containing Option A architecture, TimeSafari
integration patterns, activeDid change management, and platform-specific details.
- Added critical requirement that plugin MUST be notified of activeDid changes
- Enhanced plugin interface with onActiveDidChange() callback method
- Added clearCacheForNewIdentity() and refreshAuthenticationForNewIdentity() methods
- Updated integration examples to include activeDid change listeners
- Created comprehensive ActiveDid change requirements document covering:
* Security implications of not detecting changes
* Event-based notification pattern implementation
* Cache clearing and authentication refresh requirements
* Testing scenarios for identity switching
* Platform-specific considerations and edge cases
* Performance optimization for rapid identity changes
This addresses the critical data integrity and security requirement that the plugin
must know when TimeSafari users switch identities to prevent data leakage.
- Simplified authentication to use single activeDid instead of complex user management
- Updated plugin interface to require only setActiveDid() method
- Modified API requests to use activeDid as both issuer and recipient
- Streamlined configuration to activeDid: string instead of complex credential object
- Aligned JWT generation with simple DID-based authentication pattern
- Reduced complexity while maintaining security through DID signing
This assumption significantly simplifies the host application integration.
- Document native HTTP client implementation for Android/iOS
- Include JWT authentication strategies (Basic DID + Advanced Passkey)
- Detail API endpoint integration with TimeSafari/Endorser.ch patterns
- Cover error handling, caching, and performance optimization
- Provide migration phases and testing strategies
- Include platform-specific considerations and success criteria
This plan replaces web push implementations with native solutions
for reliable background data fetching across all target platforms.
Matthew Raymer