Dali Delivery

[Overview]

Dali Delivery is a delivery service I'm building for Jagna and nearby communities. It delivers groceries, food, clothing, and everyday goods. It's also designed to work with a partner pharmacy so customers can get medicine and prescriptions delivered. The name comes from the Bisaya word dali, meaning "quick."

[The problem]

National delivery apps barely cover small towns like Jagna. Many local stores don't have online menus or fixed price lists. Customers there also mostly pay with GCash or cash, not cards.

[How it works]

1. The customer writes a shopping list or picks items from a store's catalog.
2. The list becomes a ticket that a rider can accept.
3. While shopping, the rider updates the order live: marking items found, flagging items out of stock, and entering real prices.
4. The customer approves the final total before checkout.
5. The rider navigates to a meetup point the customer chose on a map.
6. The rider confirms the drop-off, and the customer pays by GCash, card, or cash.

[Key design decisions]

• Two kinds of orders. Catalog orders show prices upfront. Freeform list orders get prices filled in during shopping, and the customer approves the total before paying. This lets the app work with any store in town, even ones with no price list.
• Three apps, one codebase. There's a customer app, a rider app, and a web-only admin dashboard. All three share the same types and validation code in one repository.
• A separate pharmacy flow. Medicine orders are their own order type, with prescription photo upload and pharmacist verification. This keeps the business clearly in a delivery-only role under Philippine pharmacy rules.
• Payments that fit the area. Payments run through PayMongo, which handles both GCash and Visa/Mastercard. Card details stay on PayMongo's secure pages and never touch my servers.

[Tech stack]

Next.js 14 (TypeScript) · React Native + Expo · Supabase (PostgreSQL, Auth, Realtime, Storage) · PayMongo · Google Maps API · Firebase Cloud Messaging · Vercel · Expo EAS

[What's done so far]

• Full system design, including the order lifecycle, user roles, and the database approach
• Technical build brief and a 12-week MVP roadmap
• Brand identity: name, slogan, colors, and logo concept
• Research on business registration, pharmacy delivery rules (RA 10918), the Data Privacy Act, and labor rules for delivery riders

[Next up]

• The core ordering loop with live status updates
• Payments, push notifications, and map navigation
• The admin dashboard, analytics, and the pharmacy module