My roles
Product designer
Platforms
Web
iOS
Android
Date
Oct. 2025 – Present
The company had separate products for restaurants, but no single system a venue could run a full shift on. I had to design one from zero, alone and on tight deadlines.
The product serves owners, cashiers, cooks and guests. Each needs their own interface, and it still has to feel like one product. Its modules also depend on each other: the catalog feeds the POS, the POS feeds the kitchen, and loyalty runs through payment, so a change in one affects the rest. On top of that, everything has to work in a browser and in iOS and Android apps.
Four people use FortuneOS, each in a different place and on a different device.
Catalog and menu import
I designed the catalog first, because the POS is built from it: the way the owner structures the menu is the way the cashier sees it. The menu is organized into folders with a tree inside, and owners reorder it by drag and drop. I proposed giving folders colors that carry over to the POS, so cashiers find items by association.
Inside a folder, each item card holds its variations and linked modifiers, while modifiers themselves live in a separate section. To fill the catalog quickly, I designed menu import from a photo, a PDF or a spreadsheet, and worked through every state of it: processing, errors and unreadable files.
Cashier POS
I set one goal for the POS: speed. A cashier should act without stopping to think. Internal research, based on talks with cashiers and a review of other systems, showed that photos help little, if at all, so each category got a color and a name instead.
I grouped actions into three layers by purpose: what describes the order, what changes its price, and what acts on it. Each layer has a fixed place, so a cashier reaches for an action by habit. The same flow works for venues with a kitchen and without one, and for tables, takeaway and delivery. The Customers tab follows the same logic, with a loyalty program and without one.
Kitchen display
I designed the kitchen display from scratch and built it directly in code. It replaces paper tickets and shows orders in real time. I laid out the grid like a page: orders fill columns top to bottom, left to right, and the oldest stay on top.
Everything is sized for a kitchen. The screen reads from a distance, and tap targets fit a cook in gloves. Color works as the timer, turning cards from green to amber to red as an order ages. Cards never move or scroll, and overflow goes to the next page, so staff always find an order where they left it.
FortuneOS is already in real use: three venues run their shifts on it ahead of the public launch.