← All projects

Marketplace / delivery operations

Vaina

A delivery marketplace with customer, business and driver workspaces connected by a shared order lifecycle.

BuiltSeparate order and delivery state graphs mirrored from a database migration, with customer, business and driver workspaces kept apart.

Verification notesWeb/mobile source reviewed · live payments unverified

System sketch
  1. 01Customer / business / driver
  2. 02Dispatch and order lifecycle
  3. 03Payment ledger and reconciliation
High-level source-reviewed architecture. Portfolio demos use fictional data.
vaina.demo/marketplaceDemo data · no backend

Runs entirely in your browser. Opens with fictional sample data; Regenerate builds fresh rows from the project's schema. Clears on refresh.Open full screen ↗

Authorization in this portfolio

The real business layout requires a business role before protected content renders. The demo roles share a local order and follow the source order graph. Local button permissions are not backend authorization and no charge is made.

01

Operational problem

Customers, businesses and drivers need different views of the same order. The application separates browsing, business preparation and driver delivery while retaining an explicit shared lifecycle.

02

Technical constraints

Order state and delivery state are separate graphs. A UI update cannot imply a successful charge or settlement. The portfolio uses one local order and a curated happy path; it reproduces the cancellation windows and admin-only delivery-issue resolution from the source, but not refunds, payouts or dispatch.

03

Architecture

The Vaina monorepo separates Next.js web and Expo mobile presentation from shared packages. packages/core owns delivery transition graphs and cart calculations; packages/ui supplies dark blue design tokens. The business layout requires the business role before protected content renders. That is source evidence, not a full backend authorization audit.

04

Implementation

The portfolio ports the order and delivery transition graphs from packages/core and validates every action against both. Cart subtotal and order total follow the core calculators. Customer builds a single-business cart; Business accepts and prepares; marking ready offers the delivery; adding from another business asks to replace the cart, as the app does. Cancellation follows the source windows: the customer up to confirmed, the business up to driver assignment, later requests go to review. Driver can decline, accept, pick up, deliver or report a delivery issue without changing status; only Admin resolves an issue, with a reason, as failed (after pickup), reassign (before pickup) or cancel. They do not move money or contact a dispatch service.

05

Testing

The reference core has delivery-lifecycle tests. Portfolio tests cover the full order and delivery paths, graph validation, cart math, single-business carts, offer decline and re-offer, cancellation windows, admin issue resolution, role denial and terminal-state protection. Payment sandbox validation, webhook authorization and live settlement are separate checks and were not performed.

06

Current status

The separate web and mobile sources were reviewed. The portfolio does not establish launch or pilot-stage commercial results. Stripe settlement, real dispatch and GPS behavior remain unverified here; all prices, addresses and order records in the demo are fictional.

Project links

Public demo and source links have not been approved for this portfolio.

Continue exploring

All case studies →