silent-price

byAkash Share

I want make price comparsonhvfrom like cab and auto and bike from uber and rapido and ola

Home
Home

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirement Document
Page 1 of 6

System Requirements Document (SRD)

Project Name: silent-price

1. Introduction

The silent-price project is a price comparison platform designed to help users in India, like Akash, compare ride prices for cabs, autos, and bikes across popular ride-hailing services such as Uber, Rapido, and Ola. The platform aims to provide users with a seamless experience by displaying real-time pricing options and redirecting them to the respective app with pre-filled details for booking.

This document outlines the system requirements for the silent-price project, including functional and non-functional requirements, user personas, design concepts, and technical specifications.

Page 2 of 6

2. System Overview

The silent-price platform will act as an aggregator for ride-hailing services, enabling users to:

  • Compare prices for cabs, autos, and bikes across multiple providers.
  • View real-time pricing and availability based on their pick-up and drop-off locations.
  • Redirect to the selected provider's app with all booking details pre-filled, ensuring a smooth transition for the user.

The system will leverage APIs provided by Uber, Rapido, and Ola to fetch pricing and availability data. It will also include an auto-redirect feature that ensures users are taken directly to the selected app if it is installed on their device.

Locale-specific considerations, such as currency (INR) and timezone (IST), will be implemented to cater to the Indian audience.

3. Functional Requirements

As story points:

  • As a User, I should be able to enter my pick-up and drop-off locations to view ride options.
  • As a User, I should be able to compare prices for cabs, autos, and bikes across Uber, Rapido, and Ola.
  • As a User, I should be able to filter results by lowest cost, fastest ride, or preferred vehicle type.
  • As a User, I should be able to click on a ride option and be redirected to the respective app with all details pre-filled.
  • As a User, I should be notified if the selected app is not installed and be provided with an option to download it.
  • As an Admin, I should be able to manage API keys and monitor API usage for Uber, Rapido, and Ola integrations.
  • As an Admin, I should be able to view analytics on user preferences and app usage trends.

4. User Personas

Page 3 of 6

1. Regular User

  • Description: A commuter who frequently uses ride-hailing services and wants to save time and money by comparing prices.
  • Goals: Quick price comparison, seamless redirection to booking apps, and access to the best deals.

2. Admin

  • Description: A system administrator responsible for managing API integrations, monitoring system performance, and analyzing user data.
  • Goals: Ensure smooth operation of the platform, maintain API keys, and generate insights for business decisions.

5. Visuals Colors and Theme

The silent-price platform will use a unique color palette that reflects trust, efficiency, and modernity. The colors are designed to create a clean and user-friendly interface.

  • Background: #F5F9FF (Soft Sky Blue)
  • Surface: #FFFFFF (Pure White)
  • Text: #2C3E50 (Deep Navy)
  • Accent: #FF6F61 (Vibrant Coral)
  • Muted: #B0BEC5 (Cool Gray)

This palette ensures high readability and a visually appealing experience for users.

6. Signature Design Concept

The silent-price homepage will feature an interactive map-based interface that dynamically updates as users input their pick-up and drop-off locations.

Page 4 of 6

Key Features:

  1. Animated Map:

    • A live map that highlights the user's pick-up and drop-off points with animated markers.
    • As users type their locations, the map zooms in and adjusts to show the route.
  2. Floating Price Cards:

    • Price options for cabs, autos, and bikes will appear as floating cards over the map.
    • Cards will have a "flip" animation when users hover over them, revealing additional details like estimated time of arrival and vehicle type.
  3. Seamless Transitions:

    • Clicking on a price card will trigger a smooth transition effect, where the card expands to fill the screen and displays a "Redirecting to [App Name]" message.
  4. Micro-Interactions:

    • Subtle animations, such as pulsating markers and hover effects, will make the interface feel alive and engaging.

This design ensures that users are captivated from the moment they land on the homepage, while also providing a highly functional and intuitive experience.

Page 5 of 6

7. Non-Functional Requirements

  • The system should handle up to 10,000 concurrent users without performance degradation.
  • API response times should not exceed 2 seconds for fetching price data.
  • The platform should comply with data privacy regulations, including GDPR and India’s IT Act.
  • The system should be optimized for both web and mobile platforms.

8. Tech Stack

Frontend:

  • React for Web
  • React Native for Mobile App

Backend:

  • Python
  • FastAPI

Database:

  • MySQL (with Alembic for migrations)

AI Models:

  • GPT 5.4 for user-friendly responses
Page 6 of 6

AI Tools:

  • Litellm for LLM Routing
  • Langchain

Orchestration:

  • Docker for local orchestration
  • Kubernetes for server-side orchestration

9. Assumptions and Constraints

  • Users must have the respective ride-hailing apps (Uber, Rapido, Ola) installed on their devices for the auto-redirect feature to work.
  • The platform will rely on APIs provided by Uber, Rapido, and Ola, and any changes to these APIs may impact functionality.
  • The system assumes that users have a stable internet connection for real-time price fetching and redirection.

10. Glossary

  • API: Application Programming Interface, used for communication between the platform and ride-hailing services.
  • Auto-Redirect: A feature that redirects users to the selected app with pre-filled booking details.
  • Pick-Up Location: The starting point of the user's journey.
  • Drop-Off Location: The destination point of the user's journey.
  • LLM: Large Language Model, used for generating user-friendly responses.
Home design preview
Login: Sign In
Dashboard: View Analytics
Dashboard: Monitor API Usage
API Manager: Manage Keys
API Manager: Update Config
Analytics: View Trends