Bug #4797
Bug #4792: Parallel Trip Location Update Strategy Using Firebase Realtime DB
IOS Driver:- Parallel Trip Location Update Strategy Using Firebase Realtime DB
Start date:
05/15/2025
Due date:
05/16/2025 (about 11 months late)
% Done:
0%
Estimated time:
Milestone:
Sprint 29 Tukxi Ride 2025 Apr 02 to June 27
Branch name:
sprint-29_jeevan_4797
Description
To enhance the reliability of real-time driver location tracking during trips, we are implementing a parallel location update mechanism that utilizes Firebase Realtime Database alongside the existing SocketCluster infrastructure. This approach ensures the rider app receives the most accurate and up-to-date location data, even if one channel fails temporarily.
Files
Related issues
Updated by Anupama P 11 months ago
- Subject changed from IOS Driverr:- Parallel Trip Location Update Strategy Using Firebase Realtime DB to IOS Driver:- Parallel Trip Location Update Strategy Using Firebase Realtime DB
- Branch name deleted (
Branch:- sprint-19_rahul_4795, parent:- sprint-19_staging_forRelease)