Independent product · Live · Marketplace · Web + Mobile + API
BoatRental
A live boat-charter marketplace for the UAE that I designed, built and launched on my own: website, React Native app, payments backend.
Live at boatrental.ae (opens in a new tab)- surfaces: web, mobile, API
- 3
- surfaces: web, mobile, API
- source: repos: boatrental-source, Boat-rental website
- security regression checks
- 18
- security regression checks
- source: server/security.test.ts
- languages, full RTL
- 2
- languages, full RTL
- source: client/i18n, next-intl en/ar
- Drizzle tables
- 17
- Drizzle tables
- source: shared/schema.ts

The problem
Chartering a boat in the UAE usually means WhatsApp threads, no live availability and paying a stranger by bank transfer. Owners have no tooling either: no calendar, no payouts, no way to prove they are legitimate.
My role
- Independent product: sole engineer and sole git author on all three repositories (GitHub org: BoatRental952)
- Product and UX design, database design, API, web, mobile, payments, authentication and onboarding, deployment and production operations
What it is
BoatRental is a two-sided marketplace. Renters browse verified yachts, jet skis, fishing trips and shared trips, pick a date and slot, and pay by card, Apple Pay, Google Pay or bank transfer. Owners verify their identity and boats, manage bookings, set promotions and get paid out through Stripe Connect. It is live at boatrental.ae and runs on three surfaces I built and maintain: a Next.js website, an Expo / React Native app, and an Express + PostgreSQL API on Neon.
Key features
- Category discovery (yachts, jet skis, fishing, shared trips, water sports, events) with filters
- Two booking flows: instant booking, or owner approval with timed holds that a cron job expires
- Double-booking made impossible: row lock plus a PostgreSQL exclusion constraint
- One pricing engine shared by app and server; the server is the price authority
- Stripe payment intents, Apple Pay / Google Pay, Stripe Connect owner payouts, refunds, bank transfer with owner confirmation
- KYC for owners, boats and renters (Emirates ID, boat and driver licences) with an admin review queue
- Owner dashboard: revenue, occupancy, booking requests, promotions, payout settings
- Full Arabic and English, including right-to-left layouts, on web and mobile
- Push notifications, reviews, favourites, PDF invoices
Architecture
Clients
- Expo app (iOS / Android)
- Next.js website
- Admin panel
Edge
- BFF proxy with httpOnly session
- Rate limiting + helmet
API
- Express 5 routes
- Pricing engine (shared)
- Booking state machine
- Cron: hold expiry
Data & services
- PostgreSQL + Drizzle
- Stripe / Connect
- Twilio · Postmark
- Cloudinary · Push
Stack
Mobile
Web
API
Integrations
Delivery
Engineering challenges
01
Money you can trust
A security pass found that a booking could be confirmed with a 1 AED payment, that an owner IBAN could leak, and that a booking could be taken over by another user. I closed all three: the server re-quotes every booking, the webhook checks amounts, and money is stored as numeric(12,2). Each fix is pinned by a security regression check.
02
One price, three surfaces
The app, website and server must agree down to the last fils. The pricing engine lives in a shared module that is synced into the website, and the server re-computes every quote. A mismatch surfaces while the renter is still choosing, not as an error at checkout.
03
Arabic is not an afterthought
RTL is driven by an explicit isRTL context instead of the platform auto-flip, so mixed layouts never double-flip. Arabic headings get their own typeface, and a parity test stops untranslated keys from shipping.
Screens
BoatRental is live at boatrental.ae. Every screen here was captured from the real code running locally against a throwaway database seeded with the project’s own seed scripts, so no real customer data appears. Mobile screens are the Expo app running in web mode at phone size (no Android emulator was available).
Next project
AI Sales Caller