App demo
Kingfisher TableThe Kingfisher Inn, Bungay
Table 12
What to check before the mains go out: seat 3 without cream, seat 2 without pepper, a candle with the dessert. Four guests since 7:05 PM, and separate bills have been announced.
- In the hands of
- Front-of-house server
- Shown on
- Android — title on the left, three system buttons below
- Replaces
- Replaces the docket pad, the walk to the till after every order, and the mental arithmetic when four guests want to pay separately. With seven tables occupied that is a good twenty trips down the corridor saved in an evening — and three separate bills for table 9 exist the moment somebody asks.
Everything in this demo is laid out and none of it acts: buttons only report that they have no effect in the demo, checkboxes are fixed, input fields lead nowhere. Nothing is stored, sent or fetched.
How Awelior would approach this project
The Kingfisher Inn, Bungay is invented — the way it is built is not. None of this is work delivered for a client. It is the shape we would give such a project — with the same depth, but without a client who would have to answer for it.
Where it starts
At The Kingfisher Inn, service runs on a pad and a till terminal: take the order at the table, walk to the terminal, key it in, walk back. When the kitchen takes a dish off, the waiter finds out on the second trip to the table; and when four guests want separate bills, somebody ends up sorting line items at the counter. On a full evening those walks are what makes the difference.
Decisions
Allergen labeling sits on the item, not in a footnote
The nine major allergens appear on every dish, at the point where the order is taken. A server who has to leaf through something to answer will eventually answer from memory — and that is exactly where allergen labeling loses its point.
What the kitchen has pulled is not in the list at all
Once the kitchen takes a dish off, it is locked and cannot be ordered. A notice that can be dismissed saves the kitchen nothing; the second walk to the table remains.
The seat is assigned when the order is taken
Every item belongs to a seat from the outset. Separate bills fall out of that in one step; assign only at payment time and three people end up standing over a slip of paper.
Deliberately left outNo till. The app takes orders, sends them to the kitchen and splits the bill — posting, taking money and printing happen on the till system. A payment transaction brings a certified security module, receipt obligations and retention periods with it; an ordering app that handles that on the side does not exist.
What is in it
- Screens
- 5
- Tabs
- 4
- Content blocks
- 16
- Languages
- 4
Navigation responds, including the route from the section into a single table and back. The menu, the order form, the kitchen ticket list and the bill split are fully rendered and inert; the four states have a view of their own.
How it would go on
Till system and kitchen printer
Tickets have to reach the kitchen and turnover has to reach the till. Which system leads, and what happens when a ticket is lost in transit, is the core question of this undertaking.
Menu, prices and labeling
Who maintains the menu, who takes dishes off, who answers for the allergen information. The labeling is the restaurant's responsibility; the app is the route by which it reaches the table.
Devices in service
Holders, battery life across a whole evening, wireless coverage down into the vaulted cellar — and a device somebody drops while seven tables are occupied.
An app like this for your business?
Kingfisher Table is invented — the fit is not. Apps come about exactly this way: from the routes that already exist in a business, only without the paper in between.
Sample app by Awelior. Invented business, invented data, nothing stored.