- The paper presents a tool that aggregates real-time fare and ETA data to enable cost savings of 10-15% on trips.
- It employs automated data extraction and API integration, using Python-based methods and emulated environments despite API limitations.
- The experimental results highlight practical benefits such as enhanced user decision-making through faster arrival predictions and clear fare comparisons.
Web-Based Fare Comparison for Ride-Hailing Services: Uber, Ola, and Rapido
Introduction
The paper "Fare Comparison App of Uber, Ola and Rapido" (2512.04065) presents an applied study and implementation of a web-based fare comparison tool targeting popular ride-hailing services in the Indian context. The authors identify significant friction in user ride selection due to heterogeneous pricing models, rapidly varying fare structures owing to temporal and geographical factors, and the lack of price transparency across platforms such as Uber, Ola, and Rapido. Their work aims to address these inefficiencies by aggregating real-time fare data, streamlining user decision processes, and suggesting cost-optimal ride options.
Methodology
The technical realisation is centered on a Python-based backend interfaced with both automated data extraction and publicly available APIs. Due to limitations in public access, the fare data for Ola is obtained by mirroring their public-facing pricing model, whereas Uber's fares are tested using randomly generated data points due to API access restrictions. Rapido fares are sourced from empirical data specific to Bangalore.
Data acquisition employs automation tools—Android Studio's emulator and Appium—for interaction with the ride-hailing platforms, extracting estimations based on user-input origin and destination pairs. Distance estimation for Rapido is normalized by mapping locality names to continuous numerical values, facilitating calculation of travel metrics. Fare prediction for Uber incorporates time-of-day and passenger count to approximate the platform's proprietary surge algorithms, though this is constrained by randomly generated values rather than real-time querying.
Functional testing is explicitly performed via emulated environments, ensuring consistency across test cases and systematic assessment of error handling and automation routines. Real-time estimations, including fare and ETA, are provided to users, enabling side-by-side comparison prior to ride selection.
Experimental Results and Analysis
Evaluation is based on simulated user routes within an emulator. The system demonstrates successful real-time aggregation and display of fare and ETA data. Fares for Ola and Rapido align closely with those publicly available or reported for the test region. Uber data, limited by the use of synthetic test values, does not reflect production-grade accuracy but facilitates end-to-end validation of the pipeline.
Numerical results indicate that adoption of the app's recommendations enables users to achieve an average fare savings in the range of 10–15% per trip. Additionally, the app's ETA assessment found that Uber, per the tested scenarios, typically projected faster arrival times compared to Ola and Rapido, a finding that is highlighted as a potentially influential decision factor for time-sensitive users.
The methodology, while robust in framework, is constrained in precision by the absence of genuine live API integration for Uber and partial for Rapido, introducing an element of uncertainty in the generalization of results beyond the sampled contexts (notably, Bangalore-centric data for Rapido). However, the cross-validation of fares relative to public price charts for Ola serves as a check on system veracity for at least one major platform.
Practical and Theoretical Implications
Practically, this approach directly enhances user agency in a multi-provider ride-hailing marketplace, potentially incentivizing greater competition on pricing and service among providers. The platform also lays groundwork for further real-time marketplaces where users arbitrate not only fare but also additional ride attributes (such as vehicle type, amenities, or driver rating aggregates).
Theoretically, the paper underscores challenges in standardized data-sharing across consumer-facing service APIs. It raises crucial questions about the openness of mobility platforms and the technical feasibility of fair, market-wide comparison tools—especially as providers increasingly restrict programmatic access. The authors' use of automation tools to circumvent API limitations illustrates both a workaround and a fragility in current data architectures of on-demand transport apps.
Future Directions
The study identifies several future extensions:
- Direct Ride Booking: Integration of transactional APIs to move from fare discovery to immediate booking.
- Geographical Expansion: Dissemination to cities beyond the initial deployment regions.
- Feature Extensions: Support for multi-parameter filtering (vehicle class, A/C, accessibility options), voice interfaces, and chatbot integration for assistive UX.
- Live Data Integration: Overcoming current API access barriers to ensure full real-time accuracy and coverage.
Addressing these would enhance both system fidelity and user adoption. Furthermore, deeper integration of surge, demand-supply, and real-time traffic models could enable predictive fare insights and dynamic ride recommendations.
Conclusion
The fare comparison application for Uber, Ola, and Rapido demonstrates a coherent technical approach to a pertinent user need within the Indian ride-hailing market. By aggregating and presenting comparative fare and ETA data, the app fosters cost-effective and time-efficient ride choices. Although there are inherent constraints due to incomplete access to live provider APIs, the results indicate meaningful potential for user savings and improved transparency. The framework, with further data integration and functional expansion, points toward a maturing class of meta-service applications that could reshape user interaction patterns in on-demand urban mobility.