2025Full-stack
UniRide
A carpooling platform for students on the same campus, built with one project partner.
- Context
- Students on campus make the same trips at the same times, with no way to coordinate beyond messaging groups.
- Problem
- A ride board is not enough. Seats have to be tracked as they are taken, and two people who have never met need a way to talk before they share a car.
- Approach
- A PHP application on a hand-written MVC structure, no framework. My project partner wrote the backend: routing, the ride and booking logic, authentication and the REST API. I built the JavaScript interface against that API, and we drew the database schema together before either of us started.
- Outcome
- Students can publish a trip, book a seat and message each other before the ride. Agreeing on the schema first is what let us write the two halves separately without the interfaces drifting apart.
- My role
- JavaScript interface, and the database schema with my partner. He wrote the PHP backend.
- Stack
- JavaScript
- PHP
- MVC
- MySQL
- REST
- Repository
- PHPlast commit March 2026