Skip to content
Adham Altony

Available for new builds · Cairo --:-- GMT+3

Full-Stack · Dec 2025 — ongoing

CarMate — Car-Care Booking Marketplace

Saudi car-care booking marketplace — I took over the live codebase in December 2025: integrated HyperPay and Apple Pay, redesigned the UI, security fixes — and the client keeps coming back with new scopes.

Visit live Role — Full-Stack Developer — took over the production codebase
Took over the codebase
Dec 2025
Payments integrated
HyperPay · Apple Pay
Latest scope shipped
Aug 2026
Market
Dammam / Khobar, KSA
CarMate homepage: book a car wash or full detail from vetted workshops in Dammam and Khobar

Case study

The story

CarMate is a car-care booking marketplace in Saudi Arabia: customers in Dammam and Khobar book washes and detailing at vetted workshops, workshops manage their calendars and services, and payment happens in the app. I didn’t build it — I took it over. The original development team moved on in late 2025 with the platform live, and since December 2025 every change has shipped through me.

The problem

A live marketplace with real bookings and nobody left who knew the codebase. Payments weren’t finished, booking flows failed on edge cases, and the features the business needed next had no one to build them.

The build

Take over production without a handover: read the system, then ship. Payments first — the HyperPay integration built from zero and Apple Pay carried to production — then the booking and location flows, a UI/UX redesign, security fixes, and the client’s next scope: ratings capture, a real booking lifecycle, and an admin quality view. Invoicing is in delivery now.

What it changed

  • Every deploy since December 2025 has shipped through me — the payments integration, booking flows, a UI/UX redesign, security fixes, and the August 2026 scope: ratings, the booking lifecycle, and an admin quality view.
  • Payments taken live under me: the HyperPay integration built from zero, and Apple Pay carried through its full production certificate chain — shipped December 2025.
  • The client keeps coming back with new scopes — invoicing is in delivery now, and the relationship is ongoing.

My part

  • Took over a production codebase written by a previous team, without a handover.
  • Integrated payments from zero: HyperPay for cards, and Apple Pay through its production certificates — live since December 2025.
  • Redesigned the UI/UX across the booking and appointment flows.
  • Security fixes, including hardening phone-OTP login (Twilio Verify) and SMS delivery with a CITC-registered Saudi sender.
  • Shipped the August 2026 scope: ratings capture, booking lifecycle, and an admin quality view. Building invoicing now.

What it does

  • Search vetted workshops across Dammam and Khobar
  • Booking against real workshop calendars and opening hours
  • In-app payment — Apple Pay and cards via HyperPay
  • Phone-OTP login
  • Ratings and a booking lifecycle with an admin quality view

Hard parts

  • Inheriting a live production system without its authors.
  • Saudi payment and messaging compliance — Apple Pay certificates, CITC-registered SMS senders.
  • Changing a system people actively book through without breaking it.

Stack

Next.js · TypeScript · Prisma · HyperPay + Apple Pay · Twilio Verify

Want the same arrangement, built and then run by the person who built it?

Tell me what yours runs on and what an hour of downtime costs you.