Inam Baig / projects / waymate
Mobility / Consumer App
Waymate
Subscription carpool app for recurring daily routes, live in Lahore.
100% developed with agentic engineering.
Role
Agentic Engineer · Product Manager · Technical Lead
Duration
… to Present
Domain
Transportation · Pakistan
Tech highlights
Problem
What was hard
Overview
Commuters need trusted recurring carpools with verification and safe coordination, not one off ride hailing.
Users affected
Ride hosts and passengers on repeating routes in Pakistan.
Why difficult
Realtime trip state, identity workflows, and dual sided marketplace logistics.
Existing limitations
- One off hail economics
- Trust/safety gaps
- Phone number sharing risk
Constraints
- Mobile first Pakistan
- Dual host/passenger roles
Solution
Approach
Overview
Waymate mobile + Fastify API + Postgres + Socket.IO + Firebase phone auth, with admin and website.
Architecture rationale
Transactional bookings in Postgres with Socket.IO for live coordination.
Major components
- Mobile app
- API
- Admin
- Website
- Firebase
Key capabilities
- CNIC verification
- Recurring trips
- Live tracking
- In app chat/calls
- SOS
Contribution
My contribution
Project outcome
I shipped a live subscription carpool product at waymate.pk.
What I personally owned
- I owned 100% of product and engineering with agentic engineering
- I built the backend API, product flows, admin/website coordination
Features
Key capabilities
Expand a card for implementation detail and user value.
Architecture
Interactive diagram
Zoom, pan, and select nodes to explore components and connections.
Hosts and passengers use the mobile app against a Fastify REST API and Socket.IO realtime layer on PostgreSQL/Prisma. Firebase handles phone OTP; Admin and Website surfaces support ops and marketing around the same backend.
Stack
Technology
Grouped by layer. No skill bar percentages.
Frontend
- Mobile app
- Admin
- Website
Backend
- Fastify
- Prisma
- Socket.IO
Database
- PostgreSQL
Integrations
- FirebasePhone auth
Challenges
Engineering challenges
Trusted recurring carpools instead of one off ride hailing
Why hard
Realtime trip state, dual host/passenger roles, and safety, sharing phone numbers and weak identity don't work for daily commutes.
Solution
PostgreSQL trip instances and passenger sessions, Firebase phone auth plus CNIC verification, Socket.IO for live coordination, and in app chat/calls/SOS so numbers stay private.
Result
Live subscription carpool product at waymate.pk with recurring routes and safer coordination.
Results
Outcomes
Outcomes
- Live in Lahore at waymate.pk
