📖 Afaqy Knowledge Base / Smart Taxi / Driver App
Overview
The Smart Taxi Driver App is the operational mobile application used by taxi drivers to manage trips, authenticate operational status, communicate with the Smart Taxi ecosystem, and support regulatory trip compliance.
The application acts as the operational execution layer between:
- Driver
- Vehicle meter/GPS device
- Passenger tablet
- Smart Taxi backend
- Regulatory systems (WASL)
- Admin Portal
- Client Portal
The Driver App is designed to provide a simplified operational workflow that minimizes driver distraction while maintaining trip integrity, fare synchronization, compliance validation, and real-time operational visibility.
Purpose
The Driver App enables drivers to:
- Authenticate into the Smart Taxi ecosystem
- Start and end trips
- Synchronize trip data in real time
- Manage operational trip states
- Support passenger fare transparency
- Trigger emergency workflows
- Maintain compliance synchronization
- Support operational reporting
The application continuously exchanges operational data with the Smart Taxi platform throughout the trip lifecycle.
Ecosystem Role
The Driver App operates as a core operational component within the Smart Taxi ecosystem.
It continuously synchronizes operational data with:
Passenger Tablet
The Driver App directly affects passenger-facing tablet behavior.
Driver operational events may trigger:
- Trip activation
- Fare synchronization
- Distance updates
- Trip completion workflows
- Passenger feedback activation
- Advertisement transitions
Admin Portal
Operational data generated by the Driver App becomes visible within the Admin Portal.
Administrators can monitor:
- Trip activity
- Driver operational status
- Vehicle operational state
- Fare synchronization
- Compliance workflows
- Reports and dashboards
Client Portal
Taxi companies can monitor operational fleet activity using synchronized trip and vehicle data.
Regulatory Systems (WASL)
The Driver App participates in compliance workflows including:
- Trip dispatch synchronization
- Regulatory acknowledgment tracking
- Passenger-count validation
- Compliance reporting
Hardware Layer
The Driver App operates alongside:
- GPS/meter devices
- Passenger tablets
- SIM connectivity infrastructure
- Vehicle operational profiles
Operational synchronization between these components is essential for accurate trip management.
Core Responsibilities
The Driver App supports the following operational responsibilities:
Driver Authentication
- Secure driver login
- Driver identity validation
- Operational account synchronization
- Device-session association
Trip Lifecycle Execution
- Trip initiation
- Active trip synchronization
- Trip completion
- Real-time operational updates
Fare Synchronization
The Driver App continuously exchanges fare-related information including:
- Base fare
- Distance fare
- Waiting time fare
- Long-distance fare
- VAT
- Night and weekend pricing
Passenger Experience Synchronization
The Driver App directly influences the passenger experience throughout the trip lifecycle.
Operational Connectivity
The application continuously synchronizes:
- GPS data
- Distance metrics
- Time calculations
- Trip operational states
- Backend communication events
Operational Role
Operational Objectives
The Driver App is designed to:
- Simplify driver workflows
- Reduce operational friction
- Maintain fare integrity
- Support passenger transparency
- Ensure regulatory compliance
- Maintain operational visibility
- Support accurate reporting and reconciliation
Operational Workflow Overview
The Driver App workflow generally follows this sequence:
- Driver authentication
- Vehicle and device validation
- Driver operational availability
- Trip initiation
- Passenger tablet synchronization
- Real-time trip monitoring
- Fare synchronization
- Trip completion
- Passenger feedback activation
- Compliance synchronization
- Operational archival and reporting
Operational States
The Driver App may operate through multiple operational states.
Offline State
Occurs when:
- Internet connectivity becomes unavailable
- Backend communication fails
- Device synchronization is interrupted
Operational limitations may apply during this state.
Available State
The driver is:
- Authenticated
- Connected
- Operationally available
- Ready to begin trips
Active Trip State
Occurs when a trip has been initiated; during this state:
- Fare synchronization becomes active
- Passenger tablet enters trip mode
- Distance and time calculations update continuously
- Operational monitoring becomes active
- Compliance workflows may begin
Trip Completed State
Occurs after trip completion; the system performs:
- Fare finalization
- Trip archival
- Report synchronization
- Passenger feedback activation
- Compliance completion
Operational Impact
The Driver App directly affects:
- Trip lifecycle integrity
- Passenger experience
- Fare accuracy
- Dashboard visibility
- Operational reports
- Regulatory compliance
- Vehicle operational status
Improper synchronization or operational misuse may result in:
- Missing trip records
- Fare discrepancies
- Compliance failures
- Operational visibility issues
- Incomplete reports
Best Practices
- Ensure stable internet connectivity before operations begin
- Verify successful authentication before initiating trips
- Ensure GPS and tablet devices remain operational
- Confirm trip completion before ending operational sessions
- Monitor synchronization behavior regularly
- Report operational synchronization issues immediately
Authenticated SessionsTrip LifecycleTroubleshooting