KrMob

Restaurant food ordering app

Since 2022 we have been working on the ordering app for Beets&Roots, a Berlin restaurant chain. In the app, guests order food for delivery or takeaway, or at their table, and pay online. We joined the project before launch, and since 2023 we have been developing and maintaining the app's iOS, Android and browser versions on our own.

Problems we solve

Problem: A food ordering platform takes a commission on every order a restaurant receives through it. It usually keeps the guest's contact details as well, so the restaurant cannot send that guest a discount on their next order directly.

Solution: Beets&Roots takes orders and payments in its own iOS and Android app and in the browser. Once guests create an account, the restaurant knows their order history and, with their consent, sends them notifications about discounts and new items on the menu.

Problem: To deliver orders from its own app, a restaurant would have to hire couriers and plan their shifts, which means a fixed cost and extra work.

Solution: The Beets&Roots app takes the order, and the restaurant's system books just the courier from Wolt or Uber. In the app the guest sees whether Wolt or Uber is delivering and roughly when the food will arrive, and gets a link to track the courier. If the restaurant does not deliver to the address given, the app says so and suggests pickup instead.

Problem: Many guests want to change something in their bowl, for example swap the sauce or leave out one ingredient. Over the phone, every change has to be dictated and staff must write it down correctly.

Solution: In the app, guests change the ingredients of a dish from the menu within limits set by the restaurant, or put together their own from scratch, with at least 1 base and 5 ingredients. The app keeps guests within these limits and, when an ingredient sells out, suggests a replacement from the same category. The price updates straight away.

Problem: Guests ask about allergens and nutritional values, so staff repeat the same answers many times a day.

Solution: The app shows nutritional values and allergens for every dish, and the menu can be narrowed down with filters: vegan, gluten-free, dairy-free, low carb and high protein. That way guests check for themselves what they can eat before adding anything to the basket.

Problem: At lunchtime, guests who eat on the premises have to queue at the till instead of sitting down and ordering straight from their table.

Solution: A QR code on the table opens an order with the restaurant and the table number already filled in, so staff know where to bring the food. On an iPhone without the Beets&Roots app, the same code opens an App Clip, a small part of the app that runs without a full installation from the App Store. Other phones without the app open the order in the browser.

Problem: A guest picking up takeaway does not want to stand at the counter until the kitchen has prepared the food.

Solution: In the app, guests order food for immediate pickup or for a set time and choose the restaurant on the map. They then see when the order will be ready and at which station to collect it.

Problem: A restaurant wants to reward the guests who come back, and for that it needs a place where each of them has an account and an order history.

Solution: In the app, guests can take out the paid beets+ subscription, billed through Recurly, and recommend the app to friends in return for a discount on their next order. Before the guest pays, the app checks every Voucherify discount code: whether it exists, has not expired, has not been used already and applies to what is in the basket.

Problem: Apple and Google regularly raise their requirements for new app versions in their stores. If an app goes years without an update, even a small fix starts with catching up on the changes that have piled up.

Solution: In 2026 we updated Flutter to 3.47, adapted the Android version to Android 17 and moved it to Gradle 9, a new release of the build tool. In the iOS version, Swift Package Manager, built into Xcode, has replaced CocoaPods for installing libraries, and the app has moved to the scene-based life cycle (UIScene), in which iOS manages each app window separately. An app built with the iOS 27 SDK, Apple's developer toolkit, will not launch without UIScene.

Logo of the Berlin restaurant chain Beets&Roots

Case study: Beets&Roots

How we did it in practice

Challenge: Beets&Roots, a Berlin restaurant chain serving bowls, wraps and salads, needed an app in which guests tailor their dish and pay online, whether they order for delivery or takeaway, or eat in. The app had to work with the sales system in which the chain manages its menu and receives orders.

Solution: We worked on the Flutter app for iOS and Android alongside the team that started the project in April 2022, and since 2023 we have been developing it on our own. After launch we added, among other things, support for delivery by Wolt and Uber couriers, Voucherify discount codes, the beets+ subscription, order ratings, company invoices, a browser version, an App Clip for the iPhone and QR code ordering at the table.

Result: More than 10,000 orders a month from 19 restaurants in 8 German cities now go through the app, which is 82% of all the chain's orders. Guests place several hundred of them at the table by scanning a QR code. Over 4,000 people pay for the beets+ subscription, and 99.81% of app sessions run without a crash. The app, with its interface in German and English, has been on the App Store and Google Play since 2022, and in August 2026 we released version 1.48.2. Guests order in the iOS and Android app, in the browser at app.beetsandroots.de or through the App Clip on the iPhone.

See the full portfolio →

Features we shipped

Menu in categories, with filters: vegan, gluten-free, dairy-free, low carb, high protein
Changing the ingredients of dishes on the menu within each category's limits, with a suggested replacement for a sold-out ingredient
Dishes put together from scratch, with at least 1 base and 5 ingredients
Nutritional values and allergens for every dish
Delivery, pickup or eat-in, with delivery and pickup also at a set time
Choosing a restaurant on a map based on the guest's location
Delivery address and minimum order value checked before payment
Delivery by Wolt and Uber couriers, with an estimated time and a tracking link
Ordering at the table via a QR code, with the table number added automatically
An App Clip on the iPhone and a browser version for guests without the app
Card, Apple Pay and Google Pay payments through Adyen
Voucherify discount codes, plus money off the next order for recommending the app to a friend
Paid beets+ subscription billed through Recurly
Reusable packaging instead of single-use, chosen with the order
Company invoices sent by email 24 hours after the order
Order history from which any order can be repeated and rated
Push notifications about discounts and new menu items, sent with the guest's consent, plus offer banners in the app
Interface in German and English

Technology

  • Flutter
  • BLoC
  • SwiftUI
  • Adyen
  • Recurly
  • Voucherify
  • Google Maps
  • Firebase
  • Sentry

Delivery time

For an ordering app with delivery, pickup and online payments we set aside 3-4 months. The schedule depends mainly on the sales system in which the restaurant manages its menu and receives orders: the more data and functions that system makes available, the less work the connection takes.

Budget

An ordering app for iOS and Android with a menu and ingredient changes, delivery, pickup and eat-in, online payments, discounts and a subscription costs roughly 4,500-9,000 EUR net. The figure assumes a connection to a sales system the restaurant already uses; if there is no such system yet, we quote building one separately. We work out of Kraków, which is why these figures sit below Western European prices. The calculator at KrMob.com/en/estimate gives a figure for your own project in Polish zloty.

Frequently asked questions

How much does a restaurant ordering app cost? +

An ordering app for iOS and Android with a menu, delivery, pickup, online payments, discounts and a subscription costs roughly 4,500-9,000 EUR net, and we set aside 3-4 months to build it. The figure assumes a connection to a sales system the restaurant already uses.

Will a restaurant's own app replace food ordering platforms? +

It does not have to. Beets&Roots takes orders in its own app and uses Wolt and Uber only for their couriers, so guests order directly from the restaurant, not through a platform. Today 82% of Beets&Roots orders are placed in the app. A restaurant can stay on the platforms, where new guests find it, and at the same time invite its regulars to its own app.

Is a dedicated ordering app worth it for every restaurant? +

No. A single restaurant with modest traffic usually manages with a platform or a ready-made online ordering system, because an app of its own only pays for itself when the same guests order regularly. It makes sense for a chain or a restaurant that has a large base of regulars and wants to reward them with discounts and a subscription.

Can guests order at the table with a QR code? +

Yes. At Beets&Roots, a QR code on the table opens an order with the restaurant and the table number already filled in, so staff know where to bring the food. Guests without the app order through the App Clip on the iPhone or in the browser.

Can the app connect to the system a restaurant already uses? +

Yes, if that system offers an API, an interface through which programs exchange data. The Beets&Roots app loads the menu from the chain's sales system and places orders there, handles payments through Adyen, the subscription through Recurly and discounts through Voucherify. Before we quote, we check what data and functions your restaurant's system makes available.

Can you take over an app from another developer? +

Yes. At Beets&Roots we joined the project before launch in 2022, and since 2023 we have been developing and maintaining the app on our own. We bill the takeover of someone else's app by the hour, on a time and material basis, because the scope of work only becomes clear after a code review.

Find out what your app would cost

In a few seconds you get a rough cost and delivery time for your app.

Go to the estimate calculator