Focus on One Corridor First
Coming soonStart with one commuter corridor to improve route density, validate demand, and learn before expanding.
Commute Matcher
Other Product, Strategy, and Technical Decisions
A broader view of the decisions shaping the product, its market entry, backend design, and future direction.
Product Strategy
Market Entry and Growth
Build Trust Before Expanding the Network
Coming soonStrengthen verification, accountability, and safety processes before scaling to more users and locations.
Daily Commuting Instead of General Ride Sharing
Coming soonFocus the product on recurring work journeys rather than occasional or on-demand trips.
Supporting Technical Decisions
Backend Clarity and Data Integrity
created_by Instead of user_id
Coming soonUse a field name that clearly records who created a route instead of implying ownership or a general user relationship.
Backend-Controlled Seat Availability
Coming soonKeep seat calculations on the server to maintain accurate availability and reduce the risk of overbooking.
Role-Based Access Control
Coming soonRestrict sensitive actions according to the authenticated user's role and permissions.
Foreign-Key Relationships
Coming soonMaintain valid relationships between users, routes, bookings, payments, and verification records.
Future Considerations
Planned Improvements and Exploration
Low-Connectivity Support
PlannedDesign clearer retry, timeout, and failure-recovery behaviour for weak network conditions.
Notification Reliability
PlannedImprove delivery handling for booking confirmations, route changes, and cancellations.
Idempotent Booking Requests
PlannedPrevent duplicate bookings when users retry requests after delays or connection failures.
Advanced Verification
FutureExplore document expiry tracking, automated checks, reminders, and risk-based reviews.
Incident Reporting and Reputation Signals
FutureIntroduce reporting, ratings, reviews, account restrictions, and dispute-resolution workflows.