Case study · Client product work
Designing Eleanor: a sweets shop's whole menu, ordered from a phone
Eleanor Pastries wanted to sell its full range across Tripoli without opening a new branch. I designed its Arabic-first ordering app, from the first discovery meeting to the developer handoff.



- Client
- Eleanor Pastries, Tripoli
حلويات إلينور - Role
- UI/UX designer, end to end
- Platform
- iOS, Android and web, Arabic first
- Timeline
- Oct – Nov 2026
- Status
- Handed off · in development
The challenge
Eleanor sells luxury sweets in Tripoli, and every order went through a person. Customers ordered at the till or by phone. Custom cakes went to sales staff as a photo; staff checked with the factory and called back. Loyalty lived on paper and keychain cards.
The owner's goal was clear: sell the full range online with delivery. An app costs far less than a new branch, which would cost 500–600k LYD, and it reaches more of the city.
The solution
An Arabic-first app where one dish is the hero of every screen. It runs on the shop's real Odoo catalogue: 281 products in 13 categories, with real names and prices.
The hard parts are built in: cake sizes and inscriptions, special requests approved by the factory, wedding orders booked months ahead, five ways to pay, and loyalty that finally leaves the paper card.
01
281 products, one dish at a time
A shop this size can look like a spreadsheet. I made every screen calm and white so the food carries the colour. Categories sit in one row, and search is always one tap away.


02
Cakes the way people actually order them
Sizes come from the real catalogue. Two to four sizes become simple pills, and long lists become a menu. A cake can carry an inscription. Anything custom becomes a special request, with a photo and a description, that the factory approves in the app instead of over the phone.



03
Checkout that matches how Tripoli pays
Delivery or pickup, a time slot, then the payment people really use: cash to the driver, bank transfer with a receipt upload that staff confirm, or a call back from customer service. Each one has its own clear state after the order.



04
Weddings booked months ahead, and loyalty off paper
Occasion orders are a big part of the business and are booked four to five months ahead. They get their own flow: choose products, set quantities and packaging, then receive a quote. Loyalty moves into the app: 5% of spend comes back as credit that can part-pay the next order.



Try it yourself
The real prototype, running here
This is the working Direction B app I handed off. Browse, add a cake, choose a size, and check out.
- Sign in: phone 0912345678, code 482731
- Demo data · nothing reaches the real shop
- In Arabic, built for a phone
In the making
How it got here
Discovery
25 questions with the owner
We answered them together on a FigJam board: goals, customers, payment, delivery, loyalty and what runs inside Odoo. Those answers became the written v1 spec.
Directions
Four looks, one choice
I explored four directions, A to D, and chose D: one dish as the hero of each screen on a calm background.
Review
Stress-tested before handoff
Every flow was reviewed for edge cases: lead times, failed payments, cancellations and quotes. Only the points that held up went into the spec.
Simplify
Less text, clearer screens
The first screens were too dense. I redid them with a clear hierarchy, a single Cart button, and four tabs.
Direction B
White and ink, food in colour
The final look keeps the interface monochrome so only the photos carry colour. It uses the shop's real catalogue and prices.
How I worked with AI
Build
Claude and Codex turned my direction into screens and the working prototype. I reviewed every screen and sent it back until it was right.
Review
Two AI reviewers argued the UX. I applied only the points both agreed on and decided the rest myself.
Photos
The product photos are illustrations generated to match the shop's own burgundy Facebook style. Fifteen products use the shop's real photos.
The brand in the app
Quiet, so the sweets can be loud
Readex Pro for headings and IBM Plex Sans Arabic for text. The interface stays in white and ink, and every colour comes from the food.
- White
#FFFFFF - Paper
#F1EEEA - Grey
#8E8782 - Ink
#1C1816
What I shipped
A complete handoff on 6 November 2026, so the owner and his developers can build it as designed.
- Phone appThe customer app for iPhone and Android, every flow working on demo data
- WebsiteThe same shop for desktop, tablet and phone
- Landing pageIntroduces Eleanor in Arabic and English
- Handoff guideWhat is real, what is demo, and how to connect it to Odoo