Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/DavidCevallos15/Crucidrive---APP/llms.txt

Use this file to discover all available pages before exploring further.

CruciDrive is a hyperlocal mobility platform built specifically for Crucita, a coastal parish in Manabí, Ecuador, where tricimoto taxis are the primary form of public transport. Instead of the longstanding practice of drivers aimlessly patrolling streets in search of passengers — a habit locals call “vuelteo” — CruciDrive centralizes dispatch through a demand-driven mobile app that connects passengers and drivers instantly, using geographic proximity as the sole matching criterion.

The Problem

Tricimoto transport in Crucita operates without any digital infrastructure. Drivers burn fuel and wear down their vehicles cruising unpredictably through the parish, while passengers stand on street corners with no way to know if or when a ride will arrive. This creates three compounding issues:
  • Citizen safety gaps — There is no auditable record of which driver carried which passenger, on which route, or at what time. In the event of an incident, tracing a trip is impossible.
  • Economic inefficiency — Continuous random patrolling (“vuelteo”) generates excessive fuel consumption and accelerated mechanical wear, eating directly into drivers’ daily margins.
  • No accountability layer — Neither the municipality nor a cooperative has visibility into fleet location, trip volume, or driver behavior in real time.

The Solution

CruciDrive replaces vuelteo with a structured, demand-driven dispatch system built on four core capabilities:
  • Proximity-based ride matching — When a passenger requests a trip, the system surfaces the nearest available tricimoto drivers, eliminating unnecessary patrolling.
  • Phone OTP authentication — All users — passengers and drivers alike — verify their identity via SMS one-time password through Supabase Auth, requiring no email address or username.
  • Real-time GPS tracking — Drivers broadcast their live coordinates via Socket.io WebSockets, and the passenger’s map updates continuously during the ride.
  • Fixed tariffs — Fares are set at the time of ride creation and stored in the database, eliminating negotiation friction and ensuring transparency.
  • In-ride chat — A per-trip chat thread (Socket.io rooms backed by Supabase) lets passenger and driver coordinate without exchanging personal phone numbers.
CruciDrive is built in strict compliance with Ecuador’s Ley Orgánica de Protección de Datos Personales (LOPDP). Sensitive user data is encrypted with AES-256, explicit consent is collected at registration, and GPS tracking is only active during confirmed rides. Users may withdraw consent at any time from within the app.

Who Is It For?

Passenger

Opens the app, taps Request Ride, and sees nearby available tricimotos on a live map. Receives a fixed fare before confirming, tracks the driver in real time, and can chat directly with the driver during the trip.

Driver

Registers their tricimoto (plate number), goes online with a single tap, and receives proximity-based ride requests. Broadcasts live GPS coordinates to the platform and earns trips without aimless street patrolling.

Administrator

Has elevated role permissions to oversee fleet status, review trip history, manage driver profiles, and monitor platform health. Admin accounts are assigned directly in the database via the rol field in the perfiles table.

Tech Stack

LayerTechnologyRole in CruciDrive
Mobile AppReact Native (Expo 57)Cross-platform iOS and Android client
Backend APINode.js + Express 5REST endpoints and Socket.io server
DatabasePostgreSQL + PostGISRelational data and geospatial proximity queries
AuthSupabase AuthPhone OTP login and JWT issuance
Real-timeSocket.io 4Live GPS broadcasts and in-ride chat
State ManagementZustand 5Frontend global state (rides, user session, map)
UI SystemNativeWind + expo-blurGlassmorphic design — translucent cards, backdrop blur, 60 fps animations via Reanimated

Project Status

CruciDrive is currently in its MVP / Technical Proof of Concept phase. Development follows a closed Scrum timeline of 6 months (24 weeks), organized into 12 two-week sprints. Drivers self-register by validating their identity over SMS and explicitly accepting the GPS tracking terms of service. A field pilot is planned for Month 5, deploying the platform with 10 real tricimotos in Crucita parish to evaluate usability, acceptance, and real-world performance before a broader rollout. The initial infrastructure cost is **0,leveragingtheSupabasefreetierandRendersfreehostingtier.Longtermsustainabilityisfundedthroughamicrotechnologyfeeof0**, leveraging the Supabase free tier and Render's free hosting tier. Long-term sustainability is funded through a micro-technology fee of 5/month per active tricimoto unit.

Next Steps

Quickstart

Clone the monorepo, configure your environment variables, and have the backend and Expo app running locally in minutes.

Architecture

Explore the monorepo structure, data flow diagrams, database schema, and security model in depth.

Build docs developers (and LLMs) love