meta-price System Requirements Document

1. Introduction

The "meta-price" project aims to develop a comprehensive platform for comparing prices from various ride-sharing services, including Ola, Uber, and Rapido. This document outlines the system requirements necessary to achieve the project's objectives.

2. System Overview

The meta-price platform will provide users with real-time price comparisons across multiple ride-sharing services, enabling them to make informed decisions based on cost, availability, and estimated time of arrival. The system will be designed to cater to users in India, considering local currency (INR) and time zones.

3. Functional Requirements as Story Points

• As a User, I should be able to input my pickup and drop-off locations to receive price comparisons from Ola, Uber, and Rapido.
• As a User, I should be able to view estimated arrival times for each ride option.
• As a User, I should be able to see the availability of ride options in my area.
• As a User, I should be able to filter ride options based on price, estimated time of arrival, and service provider.
• As a User, I should be able to receive notifications for price changes or availability updates.
• As a User, I should be able to save my favorite routes for quick access to price comparisons.

4. User Personas

• Regular User: Individuals who frequently use ride-sharing services and are looking for the best price and service.
• Occasional User: Individuals who use ride-sharing services occasionally and need assistance in choosing the best option.
• Admin: Responsible for managing the platform, updating service provider APIs, and handling user queries.

5. Core User Flows

• User inputs pickup and drop-off locations -> System fetches price data from Ola, Uber, and Rapido -> User views price comparison -> User selects preferred ride option.
• User saves a route -> System stores route details -> User accesses saved routes for quick comparison.

6. Visuals Colors and Theme

• primary: #1E90FF (Dodger Blue)
• primary_light: #63B8FF (Light Dodger Blue)
• secondary: #FFD700 (Gold)
• accent: #FF4500 (Orange Red)
• highlight: #32CD32 (Lime Green)
• bg: #F0F8FF (Alice Blue)
• surface: #FFFFFF (White)
• text: #000000 (Black)
• text_muted: #696969 (Dim Gray)
• border: #D3D3D3 (Light Gray)

7. Signature Design Concept

The homepage of the meta-price platform will feature an interactive map where users can visualize the routes and price comparisons in real-time. The map will dynamically update as users input different locations, with animated lines tracing the potential routes. Hovering over a route will display detailed pricing and time estimates. This interactive experience will be built using motion/react for smooth animations and transitions.

Landing Hero Motion Brief

The landing page will feature a dynamic illustration of a cityscape with animated cars moving along the roads. As users enter their locations, the cars will adjust their paths to reflect the selected routes, showcasing the transformation from input to outcome. The animation will loop every 10 seconds, providing a continuous and engaging visual narrative. The reduced-motion state will simplify the animation to static lines and icons for accessibility.

8. Interaction Model & Motion Direction

• Intended Interaction Model: Animated
• The landing page will feature moderate scroll-triggered reveals and hover transitions, enhancing user engagement without overwhelming them. Interactive elements will have spring physics for a polished feel.

9. Non-Functional Requirements

• The system must handle a high volume of concurrent users without performance degradation.
• The platform should ensure data accuracy and timely updates from service provider APIs.
• The user interface must be responsive and accessible across various devices and screen sizes.

10. Tech Stack

• Frontend: React for Web
• Backend: FastAPI
• Database: MySQL or MariaDB, using Alembic for migrations
• AI Models: GPT 5.4 for user-friendly responses
• Local Orchestration: Docker, docker-compose
• Server-side Orchestration: Kubernetes

11. Assumptions and Constraints

• The platform assumes reliable API access to Ola, Uber, and Rapido for real-time data.
• The system is constrained by the rate limits and data availability of the service providers' APIs.

12. Glossary

• API: Application Programming Interface, a set of rules that allows different software entities to communicate.
• ETA: Estimated Time of Arrival, the time when a ride is expected to reach the user's location.
• INR: Indian Rupee, the currency used in India.
• Ride-sharing services: Platforms like Ola, Uber, and Rapido that offer transportation services via a mobile app.