Barqly

Barqly is a multi-sided food delivery platform built for Nigerian cities, starting with Ibadan. It connects customers, restaurants and vendors, riders, and internal operations teams through a full product ecosystem: customer app, vendor app, rider app, admin panels, CRM workflows, landing website, and web app experiences.

This was not built as a simple food-ordering clone. Barqly handles the operational complexity behind a real delivery marketplace: user onboarding, restaurant and vendor management, product catalogs, cart and checkout, payments, order lifecycle, rider dispatch, delivery tracking, support workflows, payouts, verification, notifications, and role-based access for teams.

Complexity Handled

Built and connected multiple product surfaces:

• Customer mobile app for browsing restaurants, ordering food, checkout, payment, order history, wallet, support, referrals, and notifications.
• Vendor mobile app for restaurant onboarding, product and menu management, order handling, payouts, reviews, team access, business details, and operational settings.
• Rider mobile app for onboarding, verification, availability, job acceptance, active delivery flow, earnings, payout history, ratings, and support.
• Admin and logistics panels for managing users, vendors, riders, orders, zones, verifications, payouts, support, analytics, marketing, homepage content, referrals, and platform settings.
• Web app parity for customer, vendor, rider, and admin workflows, giving the platform usable browser-based access in addition to native mobile apps.
• Landing page and public website for brand presence, customer acquisition, vendor onboarding, rider onboarding, legal pages, and company information.

Technical Scope

The system includes frontend, backend, mobile, product design, UX flows, deployment preparation, and operational tooling.

Core areas handled:

• Multi-role authentication and authorization.
• Customer, vendor, rider, and admin role separation.
• Restaurant discovery and product catalog flows.
• Cart, checkout, payment, refund, and wallet logic.
• Order lifecycle and delivery status management.
• Rider assignment and dispatch-related workflows.
• Push notifications and real-time updates.
• Vendor verification and rider verification workflows.
• Payout and bank account handling.
• Support ticket flows and CRM-style admin operations.
• Homepage and content management for platform merchandising.
• Location, maps, delivery zones, and service-area logic.
• Production backend structure with API, worker, Redis queue, MongoDB, Socket.IO, Docker, and deployment scripts.

What This Demonstrates

Barqly demonstrates the ability to operate as a full-stack product builder, not just a frontend or backend developer. The project required ownership across product strategy, UX and UI design, design system decisions, mobile app engineering, backend architecture, database modeling, admin operations, marketplace workflows, logistics workflows, payment and payout systems, production deployment thinking, QA, release planning, and AI-assisted development orchestration.

Building this single-handedly shows the ability to turn a large business idea into a working software ecosystem. It reflects the output normally expected from a small product team covering product management, design, frontend, mobile, backend, DevOps, and QA.

Public Proof

Barqly is a public food-delivery platform built for Nigerian cities, starting with Ibadan. The product is positioned for local restaurants, everyday food ordering, rider logistics, and city-level delivery operations. It serves as proof of the ability to build real marketplace infrastructure for emerging markets, not just demo software.

Short Version

Barqly is a full-stack food delivery ecosystem for Nigerian cities, starting with Ibadan. Loopxo built the customer, vendor, and rider apps, web app, logistics and admin panels, CRM workflows, landing website, backend APIs, design system, and deployment structure. The platform handles real marketplace complexity including ordering, payments, dispatch, verification, payouts, notifications, support, and role-based operations.