Portfolio index

Collaborative project record / 05

January–May 2026

BidRide

A team-based COM S 3090 coursework prototype connecting an Android/Java client to a Spring Boot and MariaDB backend for fare-bidding ride workflows across rider and driver roles.

State
Coursework prototype
Context
Team-based COM S 3090 coursework
Earlier work

Team outcomes remain separate from individual contribution.

Verified contribution

The coursework record.

Individual contribution

Het worked across the Android frontend, backend, and frontend–backend integration, including authentication, profile, ride-creation, driver-request, bidding, and account-management workflows.

Technologies and themes

  • Android
  • Java
  • Spring Boot
  • MariaDB
  • REST

Coursework integration record

BidRide's value lies in the joint: a team coursework model became a connected prototype, its seams exposed what required stronger architecture, and the lessons—not the code—carried forward.

Conceptual integration modelIllustrative · not product UI, source architecture, or a migration diagram

  1. 01 / Fare exchange

    Turn negotiation into a working coursework model

    The team prototype modeled rider-created requests with offered fares and driver-side viewing, acceptance, rejection, and counter-bidding. It demonstrated a connected coursework model, not an operating ride marketplace.

  2. 02 / Integration seam

    Carry workflows across client, service, and data

    Het worked across the Java Android client, Spring Boot backend, MariaDB persistence, and REST/JSON integration, including authentication, profiles, ride creation, driver request views, bidding, account workflows, sessions, roles, and end-to-end testing.

  3. 03 / Design consequence

    Retain the lesson, not the code

    Documented limitations around trusted client identity, non-production payment assumptions, and weak storage patterns clarified the need for stronger architecture. Vayro was later designed as a separate ground-up system; no BidRide code was reused.