Skip to content
Sabin Poudel

Index

Case study · Travel & Local

Easy Go Tours

Intercity ride-sharing in Nepal: find a ride between cities, book a seat and chat with the driver.

Role
Flutter Developer
Company
SoftUP LLC
Platforms
Android · iOS

Team project at SoftUP LLC. The work listed here is the part I built.

Built during my role as Flutter Developer at SoftUP LLC (Oct 2025 – present).

Easy Go Tours graphic, “Find a seat between cities”, showing the one-way, round-trip and city-trip ride search

Context

Easy Go Tours is an intercity ride-sharing app for Nepal. Passengers search for rides between cities and book a seat; drivers publish routes, accept requests and talk to passengers in the app. Most of it has to happen live: which vehicles are available, whether a request was accepted, and the conversation in between.

What I built

Real-time

  • A single shared Socket.IO connection with an explicit connect and disconnect lifecycle.
  • Live streaming of available vehicles.
  • A notification socket alongside Firebase Cloud Messaging push.

Rides & bookings

  • Passenger ride requests: leave a request, choose a driver, or cancel.
  • A trip and booking status lifecycle shared by passenger and driver views.
  • Paying for bookings with points, and receipt uploads.

Drivers

  • Switching the same account between driver and passenger roles.
  • Driver onboarding with licence, bluebook and vehicle document upload, each with its review state.

Messaging

  • Chat with unread counts, shared location cards and attachments.

Maps & location

  • Google Maps and device location.

Engineering notes

  1. One socket, many features

    Vehicles, ride requests, booking status and chat share a single Socket.IO connection owned by one service. Screens subscribe and unsubscribe through it instead of opening their own connections, so the app holds one connection with a clear lifecycle.

  2. A booking has a lifecycle

    Bookings move through a defined set of trip statuses, and both the passenger and the driver views render from that same lifecycle, so the two sides of a ride stay consistent.

  3. Two roles, one account

    A role switch lets one account act as a passenger or a driver. Driver onboarding tracks each document — licence, bluebook, vehicle — through its own review state.

Stack

  • Flutter
  • Dart
  • GetX
  • get_it
  • dartz
  • Socket.IO
  • Firebase Cloud Messaging
  • Google Maps
  • Hive