RoadRunner

About the client

RoadRunner is a same-day delivery service running in Louisiana, live at roadrunnerapp.com. Its tagline is "Your life delivered." The idea is simple. A customer opens the app, orders something from a nearby merchant, and a RoadRunner driver picks it up and drops it at their door. Paint from the hardware store. Groceries from the market. Supplies to the office. Same day.

The challenge

Building a same-day delivery platform is really building three products at once and making them behave like one. There is the customer app, which has to feel like DoorDash for anything. There is the driver flow, which has to hand a driver the next pickup with the right address, the right item, the right merchant contact, and give them a clean way to say "I have it" and then "I delivered it." And there is the merchant side, where a local store has to be able to accept an order without switching to a new system in the middle of a shift. The three sides only work if the system underneath keeps them all in sync in real time.

Our solution

We built the whole platform.

A React Native customer app

iOS and Android from one codebase. Address entry uses Google Places autocomplete. Payment runs through Stripe. Push notifications on delivery status use Firebase. Auth tokens and card data live in encrypted on-device storage. The app is built on modern React Native with React Navigation, animated bottom sheets for cart and checkout, and Flash List for high-performance browsing when the merchant catalog is large.

A Django backend and API

The engine underneath. Every order, every merchant, every driver, every status transition passes through the Django API. Menu and product data sync out to the customer app. Order state, payment, delivery fees, and driver assignment live here. The same backend also drives the marketing site so a customer discovering RoadRunner on the web and one already inside the app see the same catalog.

Driver dispatch and communication

When an order comes in, the backend routes it to an available driver, hands them the pickup and drop-off details, and gives them the flow to accept, mark picked up, message the customer if something changes, and mark the delivery complete. The customer sees the same status updates on their side. Nobody has to call anyone to figure out where an order is.

A Clover POS merchant integration

For merchants who already run their business on a Clover terminal, orders can land directly in the Clover POS instead of a separate app. Our custom Clover application, installed on the merchant's Clover Station, Mini, Flex, or Mobile, uses Clover's InventoryConnector and OrderConnector SDKs to sync the merchant's menu to RoadRunner and to inject incoming online orders into their live order queue. The operator sees the delivery order next to their in-store transactions, applies the correct delivery fee, and closes it out on the same tender routes. No double entry. No second system to learn. The merchant Clover app has shipped through fifteen production versions.

What makes this build different

Anyone can put a form on a website and call it a delivery service. The hard part is the three-sided coordination. The customer knowing where their order is. The driver knowing which stop is next and having a clean way to update it. The merchant getting the order in the tool they already use, not a second dashboard. RoadRunner works because those three loops close inside the same platform, and because we own every piece of it. When something needs to change, we can change it end to end.

Results

RoadRunner is live and ongoing in Louisiana. The customer app is in production on both iOS and Android. The Clover merchant app has shipped through fifteen production versions on the Clover App Market. The Django backend and driver dispatch have been running since 2021. If you have a similar three-sided problem, or a POS integration that stopped short of the finish line, we should talk.