E-Movers

The problem

What the product needed to solve

Moving and delivery services require customers and drivers to coordinate the same job while seeing different information and taking different actions.

Constraints

The realities shaping the work

• Maintain consistent job state across separate customer and driver experiences.
• Support identity, media, and real-time operational updates.
• Design clear recovery paths for interrupted or delayed workflows.

Approach

Product and technical direction

Separate Flutter applications for customers and drivers backed by Firebase authentication, Firestore, Realtime Database, and Storage.

Architecture

Clear boundaries between responsibilities

Shared domain records coordinate both applications, while authentication controls role-specific access and Firebase services support persistent jobs, time-sensitive updates, and media.

Implementation highlights

Where the engineering work mattered

• Modelled a multi-role workflow instead of treating both audiences as one interface.
• Separated durable records from time-sensitive coordination data.
• Designed reusable Flutter components around shared logistics states.

Outcome

What the work established

• Produced a coherent technical foundation for a two-sided moving and delivery service.