Learn More: https://tride-app.github.io/project
Tride is an intercity carpooling platform built around transparent trip payments and deterministic settlement. This repository contains the web application for the Tride user experience.
The App repo is responsible for presenting the product, onboarding riders and drivers, and later handling core flows such as trip discovery, booking, wallet connection, and boarding confirmation.
Intercity travel is often expensive, fragmented, and unreliable. Tride addresses that by combining:
- seat-based ride booking,
- non-custodial USDC escrow on Stellar,
- clear cancellation and no-show rules,
- off-chain coordination for profiles, messaging, and logistics.
The goal is to make intercity ride sharing feel predictable for both passengers and drivers, without requiring the platform to take custody of user funds.
This repo currently contains a Next.js frontend foundation for:
- the public-facing product experience,
- landing and marketing surfaces,
- future authenticated rider and driver flows,
- integration points for the Tride API and Soroban contracts.
- Next.js 16
- React 19
- TypeScript
- Tailwind CSS 4
- Vitest for unit tests
Install dependencies and start the development server:
npm install
npm run devThe app runs on http://localhost:3000 by default.
npm run dev
npm run build
npm run start
npm run lint
npm run test
npm run test:watchsrc/app: Next.js app router pages, layout, and shared contenttest: Vitest test filespublic: static assets
Contributions are welcome, especially in areas such as:
- rider and driver booking flows,
- wallet connection UX,
- trip search and filtering,
- responsive UI polish,
- accessibility,
- frontend test coverage.
When contributing:
- Keep changes focused on one concern.
- Run
npm run lintandnpm run testbefore opening a PR. - Prefer small, reviewable pull requests with clear descriptions.
- Preserve the product direction: escrow-first, intercity-focused, and operationally realistic.
The first Tride MVP targets a corridor such as Kaduna to Abuja. The frontend should evolve toward that concrete launch goal rather than generic ride-hailing patterns.