Sayyar
Oman's first transportation SaaS - built end to end, frontend and backend, solo.
Sayyar is a private client engagement. The live platform is the proof; implementation details are available to walk through under NDA.
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.
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.
Vite + React + TypeScript SPA, role-based routing, TanStack Table, Zod validation
Express 5 + TypeScript, two MySQL databases via Drizzle ORM
Application-level joins across a fleet DB and a passenger DB; cascade deletes across both
Mapbox GL route visualization, geolib trip matching, Arabic/English RTL via i18next
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.
| Metric | Value |
|---|---|
| MySQL databases, joined in app | 0 |
| delivered solo | FE + BE |
| languages, RTL | 0 |
| real paying client | Live |
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.
- 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.
