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

ABAJ Merchant

The restaurant floor, in your pocket.

Creator · end-to-end2026Native app · staff operations
View contribution & implementation evidence ↓
iOSAndroid
React NativeExpoExpo RouterZustand
Native app · staff operations

The restaurant floor, in your pocket.

ABAJ Merchant
iOSAndroid

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

  • Outlet staff UX
  • Native operations app
  • Order state & API integration
  • Menu availability controls
View contribution & implementation evidence ↗
ABAJ MerchantInteractive walkthrough

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

ABAJ Merchant: Outlet command center
Explore the product

Outlet command center

A daily outlet summary and quick actions lead into the staff workflow.

Latest native source · isolated staff demo

1 / 3
ABAJ Merchant · Outlet command center
Interactive walkthrough using real product captures. Screen navigation stays in this portfolio.
Feature highlights
  • Outlet command center
  • Incoming order queue & staff workflow
  • Current menu & availability controls
Built with

React Native / Expo / Expo Router / Zustand

The problem
Outlet staff need to act on orders and availability while working on the floor.
What I built
A native staff app with an outlet overview, order queue, and menu availability controls.
What it enables
Staff can inspect incoming orders and update availability from a phone.
Inspired by ABAJ Merchant?

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
  • Outlet staff UX
  • Native operations app
  • Order state & API integration
  • Menu availability controls

How the main flow works

  1. 01

    Outlet session & overview

  2. 02

    Order queue from the backend

  3. 03

    Allowed operational transitions

  4. 04

    Ready orders & menu availability

Implementation evidence

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

01 / Original screen & source

Order actions follow the state

The native order queue groups operational states and offers the next valid staff action.

Technical decision

Client transition guards mirror the server’s state rules; the backend remains authoritative.

02 / Original screen & source

Availability is an outlet operation

Current menu photography is paired with availability controls for the staff app.

Technical decision

Customer ordering and staff operations use different interfaces around the same commerce backend.

Evidence scope

Original Expo screens with a sample staff session and sample orders. The preview blocks production writes and does not change a real outlet’s availability.

Latest native source · isolated staff demo ·

The problem

Restaurant staff need incoming orders and menu availability in their hands while the kitchen and outlet keep running.

Feature highlights

  • Outlet command center
  • Incoming order queue & staff workflow
  • Current menu & availability controls

Current implementation

The Expo and React Native staff app has an outlet command center, an order queue, channel/state filters, and menu availability controls. Its Zustand state and Expo Router screens connect to ABAJ’s business APIs. This is a separate staff surface from both the customer Super App and the ERP back office.

Explore the real product

A fresh export renders the current native components with an isolated demo staff session and sample orders. The current public catalog supplies the food images and menu. Portfolio navigation does not accept real orders or alter availability.