The Viva Driver app is all set to respond its passengers over an tap. Each driver have their own login credentials . Upon activating GPS over driver app , passenger request can be received, accepted or rejected. The driver can keep track upon ongoing trip. He can manage his profile information. The details of the trip such as pick up and drop location, time, taxi type etc., are received from the passenger. The approximate fare is automatically calculated. The trip payments can be received via card or cash from passenger. The driver app allows to saves history of completed trips for future reference in statistics tab.
Some of the features of Viva Driver app includes:
Easily downloadable Driver app.
Login credentials to every Driver.
Password recovery button.
Dashboard with driver account details.
Go Online / Go offline button.
Locate themselves over google map.
Secured individual Driver profile with image, Email Id, phone number, driving license and taxi details.
Mandatory to activate GPS upon login.
Automatically receives passenger's trip request with trip details.
Confirms trip within 60 seconds or reject.
Detects passenger using GPS.
Confirms passenger pick up by clicking Accept button.
Can call Passenger.
Google navigation for ongoing trip.
Send notification upon arrival to pick up passenger.
Start trip by clicking "start trip" button.
Waiting time stop watch with auto calculation of fare.
Cash / Credit card processing with instant payment e-receipts.
A unique Trip Id number for each trip.
Saves history of completed trips for future reference in statistics.
Trip are also assigned through telephone booking.
"Continued use of GPS running in the background can dramatically decrease battery life"
Usage of Background mode location Updation:
1. Its used to track the driver location and driver will get passenger request even the app is on background mode.
2. Here admin panel getting the driver status (online or offline) by using driver location updation. If the driver went to background, that time also we need to update driver locations because the driver automatically going to idle stage when they didn't get the location within a particular seconds. In this time the driver can't able to get any passenger trip request.