Abhishek PatelPortfolio
Build.
000
Work
Transportation SaaSJul - Dec 2025Private client

Sayyar

Oman's first transportation SaaS - built end to end, frontend and backend, solo.

Sole frontend + backend developerBasira (Oman)
Visit live Private client
ViteReactTypeScriptExpress 5Drizzle ORMMySQLMapbox GLi18nextTanStack TableZodJWT
Visuals under NDA

Sayyar is a private client engagement. The live platform is the proof; implementation details are available to walk through under NDA.

01The problem

A real Omani transport startup needed to digitize bus fleet operations, passenger booking, route management and analytics - for multiple stakeholder types - on real contractual timelines.

02The solution

A complete operator platform. I was the sole developer on both the frontend dashboard and the backend API: fleet, bookings, payments, live routes on Mapbox, and full Arabic/English RTL support, backed by a dual-database Express API.

03Architecture
Frontend

Vite + React + TypeScript SPA, role-based routing, TanStack Table, Zod validation

Backend

Express 5 + TypeScript, two MySQL databases via Drizzle ORM

Cross-DB

Application-level joins across a fleet DB and a passenger DB; cascade deletes across both

Maps & i18n

Mapbox GL route visualization, geolib trip matching, Arabic/English RTL via i18next

04Key features

Operator dashboard

Passengers, owners, companies, captains, buses, routes, trips, bookings, payments, analytics.

Live route maps

Mapbox GL trip visualization with overlapping-marker handling.

RTL i18n

Full Arabic / English with right-to-left layout support.

Multi-modal booking

One-way, round-trip and day/week/month subscription flows.

05Results
MetricValue
MySQL databases, joined in app0
delivered soloFE + BE
languages, RTL0
real paying clientLive
06My role

I owned the whole stack. On the frontend: the full admin dashboard, Mapbox route visualization, RTL i18n, role-based protection, TanStack tables and Zod validation. On the backend: an Express 5 API over two MySQL databases with Drizzle, JWT auth with server-side invalidation, geolib-based trip matching, and cross-database join logic for subscription bookings.

07What I learned
  • Cross-database joins in application code are doable but demand careful, explicit sequencing.
  • RTL is a layout discipline, not a translation step - it has to be designed in from the start.
08FAQ

Want the deeper story?

Ask my AI about Sayyar for specifics, or reach out directly.

Get in touch
Next project
StarTech