Project

General

Profile

Bug #4792

Parallel Trip Location Update Strategy Using Firebase Realtime DB

Added by Anupama P 11 months ago. Updated 9 months ago.

Status:
Resolved
Priority:
Normal
Target version:
Start date:
05/13/2025
Due date:
07/17/2025 (about 9 months late)
% Done:

25%

Estimated time:
(Total: 0.00 h)
Milestone:
Sprint 29 Tukxi Ride 2025 Apr 02 to June 27
Branch name:

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.


Subtasks

Bug #4795: Android Driver:- Parallel Trip Location Update Strategy Using Firebase Realtime DBQA PassedAnupama P05/13/202505/13/2025

Actions
Bug #4796: Android Rider:- Parallel Trip Location Update Strategy Using Firebase Realtime DBQA PassedAnupama P05/14/202505/14/2025

Actions
Bug #4797: IOS Driver:- Parallel Trip Location Update Strategy Using Firebase Realtime DBQA ReadyAnjali M05/15/202505/16/2025

Actions
Bug #4798: IOS Rider:- Parallel Trip Location Update Strategy Using Firebase Realtime DBQA PassedJeevan C Paul07/17/202507/17/2025

Actions
#1

Updated by Anupama P 11 months ago

  • Description updated (diff)
#3

Updated by Anandhu P Kumar 11 months ago

  • Status changed from New to In Progress
#4

Updated by Anandhu P Kumar 9 months ago

  • Status changed from In Progress to Resolved

Parallel Trip Location Update Strategy Using Firebase Realtime DB integrated.

Also available in: Atom PDF