
Maasob Al-Sultan: a restaurant app built for how the Saudi market actually works
An ordering app for a Hijazi breakfast chain in Jeddah: five branches, an AI assistant with a name — Sultan AI — calorie counts on every item, loyalty that pays out at 100 points, and a bill that separates VAT from delivery. Shipped January 2026 and still being updated.

Maasob Al-Sultan is a restaurant chain in Jeddah serving Hijazi breakfast — maasob with cream, honey, banana or cheese, alongside mutabbaq and other dishes. Like most restaurants in the Gulf, it was selling through the aggregators: a commission on every order, and a customer you stop knowing anything about the moment they leave an app you do not own.
The chain's own app went live on the App Store and Google Play in January 2026, with all five branches on it from launch, after under a month of work.
What the customer sees




The details that decide it
The headline features appear in every pitch deck. What separates an app people use from one they install and forget is the small stuff that deals with how the market really works:
Sultan AI — an assistant with a name
It appears in the interface as "ask the chef", not an anonymous chat bubble in the corner. Running on Gemini, it answers what used to tie up the branch phone: what is in this dish, where is my order, what suits a group of six.
Calories on every item
326 for the cheese mutabbaq, 427 for the tuna. Calorie display is a regulatory requirement for food outlets in Saudi Arabia, and building it into the menu structure from the start is far cheaper than retrofitting it across a finished catalogue.
Loyalty with a visible line
100 points for a free meal, with the counter sitting in the cart the whole time. Clarity matters more than generosity here — the customer knows exactly how far away the reward is.
Branch opening hours
Outside working hours you can still browse and fill a cart, with a clear notice that it will be fulfilled when the branch opens. The alternative — an app that looks broken for half the day — loses a customer exactly once.
An honest bill
Subtotal, VAT and delivery each on their own line. A number that surprises someone at checkout is among the most common reasons a cart is abandoned.
Five branches, one flow
The customer picks a branch and the order lands on that branch's screen. A correct order in the app that arrives confused in the kitchen is a failed order, however good the interface was.
The stack, and why each piece
Flutter
One codebase, and more to the point one release queue. Two native builds means two review cycles to align, and on a one-month schedule the aligning is what kills you — not the code.
Firebase
Realtime data, so an order appears at the branch the moment it is placed and an item that runs out disappears from the menu while it matters.
Paymob
A payment gateway built for this region rather than adapted to it. Local cards and wallets work first time, which is most of the checkout battle.
Gemini
The model behind Sultan AI, answering customers at 1am without a support desk waiting behind the screen.
After launch
Shipping fast counts for nothing if the app stops there. Version one went out in January 2026; the app now sits at 1.1.6 — updates kept coming for months after launch, which is the difference between a product in service and a project that was delivered and closed.
Common questions
How long did the Maasob Al-Sultan app take?
Under a month from the start of work to launch on the App Store and Google Play in January 2026, with all five branches connected from day one.
What was it built with?
Flutter for iOS and Android from one codebase, Firebase for realtime order data, Paymob for payments, and Gemini behind the Sultan AI assistant.
What does the app do?
Ordering across five branches on one system, an in-app AI assistant, calorie counts on every item, a 100-point loyalty programme, in-app ratings, a bill that itemises VAT and delivery separately, and per-branch opening hours.
Why would a restaurant build its own app instead of using delivery aggregators?
The commission on every order, and the fact that the customer relationship and the data stay with the aggregator. Owning the app keeps the margin and the data, which is what makes loyalty or repeat custom possible at all.
Does the app show calorie counts?
Yes, on every menu item — a regulatory requirement for food outlets in Saudi Arabia, handled inside the menu structure from the beginning.
Working on something like this?
hello@ahmedali.online