← Selected work

Freight marketplace · Fleet operations · Geolocation

EASY-TRUCK

Connect the freight market to what happens on the road.

EASY-TRUCK brings the commercial and operational sides of road freight in Cameroon into one platform. My contribution spans the web and mobile experiences, geolocation, business workflows and engineering foundations needed to keep the marketplace, field operations and financial follow-through coherent.

Organization
My Talents Academy · Road freight in Cameroon
Role
Full-stack & DevOps engineering
Scope
19 backend applications · 2 web portals · 2 native Android apps
Product
Marketplace · Fleet · GPS tracking · Payments

System overview

Platform overview — product capabilities

Four connected experiences, from finding transport to resolving a delivery.

  • Shipper app

    Find transport, compare offers, pay and follow the delivery.

  • Fleet portal

    Manage vehicles, drivers, capacity and dispatch.

  • Driver app

    Follow the mission, share GPS positions and record evidence.

  • Admin console

    Oversee operations, verification, finance and support.

One transport journey, with a distinct view and permissions for each participant.

  • Freight marketplace

    Geographic search, compatible capacity, matching and negotiation.

  • Fleet and dispatch

    Vehicles, drivers, availability, eligibility and assignment.

  • Maps and GPS tracking

    Live positions, routes, remaining distance and estimated arrival.

  • Field evidence

    Photos, signatures and queued GPS points and proofs when offline.

  • Payments and settlement

    Mobile Money, advances, balances, commissions and refund workflows.

  • Trust and oversight

    Verification, mission messages, incidents, disputes and ratings.

Build a connected transport operation around the marketplace.

Finding a truck is one part of a freight journey. The product also has to establish who can carry the goods, when the vehicle is available, who will drive, where the shipment is and what happens when delivery or payment does not go as planned.

I worked across that journey and the systems behind it. The platform connects individual and company shippers, independent carriers, transport companies, dispatchers, drivers and platform administrators through four dedicated applications.

Bring the right freight, vehicle and commercial terms together.

Shippers publish freight requests and search available transport geographically. Carriers publish capacity and receive compatible freight suggestions. Matching takes route, timing and load requirements into account, including weight, volume and vehicle suitability such as refrigerated transport.

Offers and counter-offers support negotiation before booking. Carrier ratings and indicative price ranges help inform the decision; historical estimates can explicitly abstain when the available data is insufficient. Vehicle and driver availability are checked again before resources are committed.

Turn a position on a map into useful operational visibility.

The driver app captures GPS positions during an active mission. The shipper, fleet and operations team see the views appropriate to their role: a fleet overview or an individual mission, route legs, remaining distance and estimated arrival, with route-deviation information for authorized operational users.

Maps follow the moving vehicle and allow a return to the full route. They distinguish a fresh position from a delayed or unavailable signal. The mapping and routing foundation uses MapLibre and self-hosted OpenStreetMap data, with location search down to neighbourhoods.

An experimental road-discovery pipeline also studies aggregated GPS traces to identify roads missing from the base map. It remains in validation; it is separate from the implemented mission-tracking journey.

Keep delivery evidence usable when connectivity drops.

The driver experience brings the current mission, the next action, the itinerary and proof capture together. Loading and delivery records can include photographs, a recipient signature and outcomes such as delivery with reservations, partial delivery or refusal.

GPS points and delivery proofs have persistent, protected local queues and resume synchronization when connectivity returns. The interface distinguishes evidence saved on the phone from evidence received by the platform. Mission messages and notifications connect the parties, while incidents and support requests keep exceptions attached to the operational context.

Carry the commercial agreement through payment and delivery exceptions.

The financial workflows cover Mobile Money collection, a carrier advance, the remaining balance, commissions and financial documents. Settlement depends on the relevant mission milestones; a partial, disputed or refused delivery can hold the balance for review.

Cancellations have their own refund and compensation workflows. A replacement-carrier bidding journey is also implemented in the development environment to recover an eligible cancelled transport. Payment-provider activation and real-money qualification remain separate from these implemented flows.

Give each participant the right tools and the right level of access.

The fleet portal combines vehicle and driver management, capacity, dispatch, tracking and financial follow-up. The admin console supports company and independent-carrier review, identity and document verification, operational supervision and exception handling.

The platform also covers shared mission conversations, support-ticket exchanges, post-delivery ratings and comment moderation. Permissions follow the participant’s current role and relationship to the company, vehicle or mission, including when those relationships change.

  • Company and independent-carrier verification, supporting documents and review decisions
  • Vehicle and driver eligibility, availability and assignment controls
  • Mission messages, notifications, incidents and support conversations
  • Delivery disputes, held-balance decisions and moderated post-mission ratings

Keep a large product coherent across applications and failures.

My work also covers the engineering environment around these features: service boundaries, shared integration expectations, application-specific standards, automated checks and release tooling. Nineteen backend applications support two web portals and two native Android clients.

The important guarantees are practical: a retry must not duplicate a payment or reservation, a driver or vehicle must not be assigned to overlapping missions, and a network interruption must not silently lose a proof. Automated scenarios exercise permissions, concurrency, persistence and dependency failures, with browser checks for the web journeys.

+ Engineering principles

What the system is designed to preserve.

01

One coherent journey

Connect the commercial agreement, field execution and financial outcome.

02

Useful geolocation

Show routes, progress and signal freshness with access suited to each role.

03

Continuity in the field

Keep GPS points and delivery evidence available for synchronization after a network interruption.

04

Recoverable exceptions

Handle disputes, cancellations and uncertain outcomes without losing their history.

Next case studyDesignome