Skip to content
← All projects
/ Case study · Native appSource reviewed · October 2026

ABAJ Super App

Delivery, pickup, reservations, and catering.

Creator · end-to-end2026Native app · customer ordering
View contribution & implementation evidence ↓
iOSAndroid
React NativeExpoExpo RouterZustandNativeWind
Native app · customer ordering

Delivery, pickup, reservations, and catering.

ABAJ Super App
iOSAndroid

Designed and built by Alexanders Schwartzmann · end-to-end

  • Native customer UX
  • Expo screens & navigation
  • Cart, options & checkout
  • Commerce API integration
View contribution & implementation evidence ↗

The iOS and Android customer app brings the restaurant menu, order options, and checkout into one native experience.

ABAJ Super AppInteractive walkthrough

Choose a screen to see the product’s features and main flow.

ABAJ Super App: Four ordering modes
Explore the product

Four ordering modes

Delivery, pickup, reservation, and catering share the current menu and promotional banners.

Latest native source · current public menu

1 / 3
ABAJ Super App · Four ordering modes
Interactive walkthrough using real product captures. Screen navigation stays in this portfolio.
Feature highlights
  • Delivery, pickup, reservation & catering
  • Current menu, required variants & cart
  • Courier, schedule & payment choices
Built with

React Native / Expo / Expo Router / Zustand / NativeWind

The problem
Different ordering needs should still feel like one restaurant experience.
What I built
An iOS and Android customer app for delivery, pickup, reservations, and catering.
What it enables
Customers can choose the menu, required options, schedule, courier, and payment in one flow.
Inspired by ABAJ Super App?

Let’s build around your workflow.

Discuss a similar project
Contribution & implementation

I designed and built this project end to end.

Project creator

Alexanders Schwartzmann

From product design, UX, and architecture to the feature implementation below.

My implementation scope
  • Native customer UX
  • Expo screens & navigation
  • Cart, options & checkout
  • Commerce API integration

How the main flow works

  1. 01

    Current catalog from the backend

  2. 02

    Required item choices & cart

  3. 03

    Address, mode & schedule

  4. 04

    Order quote & checkout

Implementation evidence

The implemented feature, how it works, and the technical decision behind it.

01 / Original screen & source

Menu choices belong to the order

The app captures required choices, extras, notes, and quantities before building the checkout summary.

Technical decision

The cart carries the configuration of each dish, instead of passing only a menu name.

02 / Original screen & source

A checkout with fulfilment context

Delivery address, courier, schedule, payment choices, and totals appear in the native flow.

Technical decision

When the cart becomes empty, its voucher, points, and reservation context are cleared together to avoid stale ordering state.

Evidence scope

Original native source rendered through an isolated Expo export, using the public catalog and a local cart. The review does not submit checkout or test device hardware.

Latest native source · current public menu ·

The problem

Customers need delivery, pickup, reservations, and catering to feel like one product rather than unrelated checkout flows.

Feature highlights

  • Delivery, pickup, reservation & catering
  • Current menu, required variants & cart
  • Courier, schedule & payment choices

Current implementation

React Native, Expo, Expo Router, Zustand, and NativeWind power the customer app. The current source reads the live ERP catalog rather than a retired hardcoded menu. Required rice and sambal choices are validated before adding a dish. Checkout brings together address, courier, schedule, voucher, kitchen notes, payment choice, and total.

Explore the real product

Captures come from a fresh production web export of the current native source, using the active public menu and banners. Cart actions stay in the isolated preview; no customer checkout or payment was submitted.