marbat

Problem

Riders, trainers, and stable operators needed one product to discover services, book, and manage operations instead of fragmented tools.

What I built

Led frontend architecture and team involvement across both platforms. The web frontend is a Next.js 14, TypeScript, and Tailwind marketing site on Vercel with a hero and service sections. The mobile app is Flutter with clean architecture, Firebase auth, OTP login, and push notifications, a rider-facing experience with onboarding, service browsing, stable profiles, booking flows, order tracking, favorites, and account management.

Impact

Architected a scalable multi-platform product, mentored the team, and kept code quality consistent across web and mobile.

Key features

• •Marketing-driven Next.js landing site with hero and service sections
• •Flutter rider app: onboarding, browsing, stables, bookings, orders, favorites, account
• •Firebase authentication, OTP login, and push notifications
• •Complex booking flows and order status tracking
• •Team mentorship and shared quality bar across web and mobile

Tech stack

Challenges & solutions

• Challenge

  One product story across web marketing and a feature-heavy mobile app.

  Solution

  Clear platform boundaries: Next.js for the public site, Flutter clean architecture for rider modules, shared product language for bookings and profiles.

• Challenge

  Keeping quality high while mentoring across two codebases.

  Solution

  Reusable patterns, explicit module ownership, and reviews that covered auth, notifications, and booking edge cases.