Sizl: How We Launched a Rider App in Just 2.5 Weeks

Sizl is a Chicago-based dark kitchen network. In April 2025, we helped them rebuild their main customer app from scratch in just three months. Then, we migrated the project to React Native, added new features, and prepared the product for an investor demo. The relaunch helped Sizl secure funding, and we have been growing the product as their technical partner ever since.

The next step was a standalone riders app, which was built separately to isolate business logic and streamline operational workflows.

In a growing business ecosystem like Sizl’s, where different roles interact with the system – such as kitchens, riders, and support – merging all functionality into a single app would be both inconvenient and inefficient. That's why the client decided to create separate, tailored apps for each role with a simple, streamlined process.

This approach prevents users from becoming overwhelmed, speeds up development, and simplifies support. It also enables the team to track performance metrics for each app individually, making it easier to identify areas for improvement at each stage of the order lifecycle.

At the same time, all the apps share a single codebase. This results in reusable components, quicker deployment, and a solid foundation for long-term growth.

Read more about this approach in this article.

Our goals for this new project were:

• Build a fast and intuitive way for riders to accept orders and report completed deliveries;
• Sync the rider app with the admin panel so that riders and kitchen staff could see real-time order statuses and stay aligned throughout the process;
• Move fast by reusing the architecture and components from the main customer app.

We built and released the rider app in just 2.5 weeks by leveraging shared components from the monorepo.

Today, the Sizl rider app supports:

• 30-40 minutes

  average delivery time

Before an order is delivered by a rider, the station manager processes it via a dedicated admin panel that is synced with the app. Here’s how the process works:

In the Bundling section, there are two lists: one for ready-to-go orders and one for riders currently at the station. The packer manually groups one or more orders into a bundle and assigns it to a rider, typically the first one in line.

A map view helps group nearby addresses into efficient bundles. We plan to automate this process soon. For now, the manual process allows us to identify bottlenecks and optimize rider distribution.

To accept an order, a rider must arrive at the station and tap "Ready to Go" on their app. This update appears in the admin panel, letting the packer know who’s next in line.

Below are a few technical solutions that helped us quickly build the rider app and ensure that it runs smoothly in production.

Some areas in Chicago have spotty internet, so we added offline-first functionality. Riders can upload delivery confirmation photos without an internet connection; the app stores the data and syncs it automatically later.

While the rider is en route, customers can track their movements in real time via an in-app map that updates automatically.

While all Sizl apps are cross-platform (one of the reasons we love React Native), we made a few platform-specific tweaks for iOS – including improvements to push notification handling and background geolocation tracking.

Frontend: React Native
Design: Figma

When we launched Sizl’s delivery operations, our goal wasn’t just to hand off orders to riders; it was to build a structured, efficient process in which no one wastes time on unnecessary steps. When a rider arrives at the station, they tap a single button, and the system instantly marks them as available. The station manager sees this in the admin panel, assembles a bundle, and hands it off.

This setup improves delivery speed and gives the team better control over quality and cost. Riders return faster, kitchens stay productive, and customers receive their food on time.