DIVUZKIINDEPENDENT SOFTWARE ENGINEER
← Selected work / 03

TrayFoods

I founded TrayFoods, a campus food delivery platform connecting customers, vendors and delivery personnel. I built the Ionic applications and the Django/GraphQL backend, integrated Paystack payments with vendor and courier payouts, and onboarded 10+ vendors and 20+ student delivery personnel. Operations are currently paused.

01 / Context

The problem.

Campus food ordering involved three groups with no shared system between them: customers placing orders, vendors preparing them and student delivery personnel completing them. TrayFoods connected all three through mobile and web applications, which meant money had to reach two different kinds of recipient and dispatch had to be coordinated rather than arranged by hand.

02 / Ownership

My part in it.

Founder and CEO, and sole engineer from 2021 to 2023. The team later expanded with dedicated finance and support functions.

Founder and CEO, and sole engineer from 2021 to 2023.

03 / Constraints

The shape of the challenge.

Payments had to split into vendor and courier payouts rather than settling into a single account, and dispatch across student delivery personnel had to be automated. The product ran as a real operation, so engineering decisions carried directly into daily deliveries.

04 / Build log

What went into it.

  1. 01

    Founded and built a campus food delivery platform connecting customers, vendors and delivery personnel through Ionic mobile and web applications.

  2. 02

    Developed a Django/GraphQL backend with PostgreSQL on Railway, AWS media storage and automated CI/CD deployment.

  3. 03

    Integrated Paystack payments, vendor and courier payouts, and dispatch automation; onboarded 10+ vendors and 20+ student delivery personnel.

  4. 04

    Served as sole engineer from 2021 to 2023 and later expanded the team with dedicated finance and support functions.

05 / Decisions

What it turned on.

  • Split each payment into vendor and courier payouts.

    A single customer order pays two different kinds of recipient, not one account.

  • Automate dispatch instead of assigning couriers by hand.

    Coordination ran across student delivery personnel on a platform serving real daily deliveries.

  • Deploy through automated CI/CD on managed infrastructure.

    Daily deliveries depended on the platform, so releases had to be repeatable.

Flow / One order, end to end

How a single order moved from three participant apps through payment to dispatch.

  1. Participants

    Customers, vendors and couriers on Ionic mobile and web applications.

  2. Backend

    Django and GraphQL, PostgreSQL on Railway, AWS media storage.

  3. Payment

    Paystack captures the order payment.

  4. Payouts

    Split to vendor and courier rather than one account.

  5. Dispatch

    Automated assignment across student delivery personnel.

Divine's account of the build.

Public evidence

The App Store listing names Divine Ikhuoria as developer and seller, which supports a shipped iOS application. It is not a record of revenue, user numbers or current operations. The related Django scaling article discusses architecture choices; its concurrency target is not a measured TrayFoods traffic result.

HAVE A SYSTEM TO BUILD?

Let’s make
it work.

Selected contracts & automation

Selected software contracts and business automation. Tell me what needs to work better.

↗