Tuukaa

Business Context

Nigeria's logistics sector is one of the fastest-growing segments of the economy, driven by e-commerce growth and rising consumer expectations. However, most small-to-medium logistics operators rely on WhatsApp and phone calls for order management — a system that breaks down at scale. Tuukaa aimed to digitize this workflow for businesses that needed operational control without enterprise pricing.

The Problem

The client needed a platform that could manage multiple delivery agents, track order status in real time, allow customers to monitor their deliveries, and give operations managers a central dashboard for workflow visibility. No existing affordable solution met all these requirements for the Nigerian market context.

Approach

I designed a three-layer system: a customer-facing order tracking interface, a rider/agent mobile interface for delivery updates, and an operations dashboard for dispatch management. The architecture was built to work reliably in intermittent connectivity scenarios, a real constraint for delivery agents operating across Nigerian cities.

Technical Architecture

Built with Flutter for the mobile agent interface and a Laravel PHP backend on MySQL. Real-time order status updates are delivered via REST API polling optimised for low-data environments. The agent app runs as a native Android application with offline-capable state management. Deployed on cloud infrastructure with Nigerian region proximity for low latency.

Key Features Built

• Real-time order tracking for customers
• Dispatch and assignment workflow for operations managers
• Delivery agent mobile interface (Flutter)
• Order status notifications via SMS and email
• Performance analytics dashboard for fleet management
• Customer proof of delivery capture
• Route and zone management
• Offline-capable agent app for low-connectivity scenarios

Challenges Solved

• Built for intermittent connectivity: delivery agents frequently operate in areas with poor network coverage
• Designed a three-tier access system (customer, agent, admin) with appropriate data visibility at each level
• Implemented lightweight API calls optimised to avoid overwhelming mobile data quotas
• Created a simple agent interface usable by drivers with limited smartphone experience

Lessons Learned

Logistics software lives or dies on reliability. I learned that a system that occasionally shows incorrect delivery status is worse than having no system at all, because it destroys the operational trust that makes digital dispatch possible. This project shifted my thinking: in mission-critical mobile software, graceful offline handling and accurate state management are not features, they are the product. I also learned to design for the lowest-common-denominator device, not the flagship smartphone.