UX/UI Design · Baemingo · UX/UI design of a menu builder
Letting restaurants build the ordering menu their customers see
I designed the layout builder in the Baemingo back office: the tool where a restaurant decides how its menu looks to customers in the ordering app and self-service. Staff create categories, add products and style each category card, and see the result in a phone preview as they work. Every change saves automatically.
- My role
- UX/UI designer, alongside my role as Product Development Lead
- Year
- 2021–2022
- Industry
- Restaurant tech, B2B SaaS
- Company
- Baemingo
- Users
- Restaurant owners and staff
- Platform
- Web app, with a preview of the ordering app
- Tools
- Figma
The short version
The challenge
Restaurants had their products in the system, but needed a way to turn them into a menu that works for their customers in each sales channel, without help from Baemingo.
What I did
I designed the flow and the UI of the layout builder, from creating a layout to categories, products, styling and sort order, and tested it with users.
What it was built for
A menu that restaurant staff can build and change on their own, and see exactly as their customers will see it.
What I did as UX designer
Flows and structure
How a layout is created, named and connected to a sales channel and a menu, and how it is found and edited again later.
UI design for the back office
Finished screens for every step: the layout list, the builder, the category and product panels and the detail view.
Live preview
Two phone previews in the builder, so staff see the menu the way their customers will see it while they build it.
Interaction details
Autosave, drag and drop for sort order, a step that opens only when it can be used, and guidance on the page.
Usability test
Testing showed the order users expected: first create the products, then the layout, the menu.
Next steps
Ideas for the product backlog: visibility by service type or time, colour palettes, subcategories and app branding.
The challenge
In Baemingo, products are created once, in the product catalogue (PIM). But a list of products is not a menu. A restaurant needs to decide how the products are grouped and shown to the people ordering: in the ordering app, in a self-service kiosk or at the till.
A layout is that decision: how staff or customers experience the menu when they place an order. In a usability test, users described the order they expected to work in:
- Create the productsName, price, image, description and ingredients, in the product catalogue.
- Create a layoutWhich is the menu: the categories and products the customer sees, and how they look.
So the layout builder had to start from products that already exist, and make building a menu feel like arranging it, not like filling in forms.
Version 1 and the user test
Building menus was one of the biggest pain points for new restaurants. I designed a first version of the menu builder, tested it with users, and improved it from what we learned.
Version 1: create a menu layout
Version 1: build the menu in a phone preview
What we tested
- Is it easy to understand what to do, and how?Create the first layout: enter a name, and create it.
- Is it easy to understand the menu layout as a concept?That a layout is how the menu looks to the people ordering, separate from the products themselves.
What we learned
- Products first, then the menuUsers wanted to first create their products, and then create the layout: the menu.
- Drag and drop workedThe format, with categories and products sorted by drag and drop, held up as the menu grew.
- Help with coloursUsers asked for recommended colour palettes instead of typing hex codes.
The rest of this case shows version 2, improved from what we learned.
Create a layout
A new layout needs three things: a name, a sales channel and a menu. The sales channel list only shows the channels the company has activated, and choosing the till (POS) leads to the POS layout. Existing layouts are listed next to the form, so they are easy to find and change later. Click a screen to enlarge it.
Name the layout and pick sales channel and menu
Find and edit existing layouts
Build the menu
The builder shows the menu in two phone previews: the start of the menu with its categories, and the category that is open with its products. Panels for adding and editing open on the right, so the preview always stays in view.
Start with the first category
Style the category card
Add products to the category
Change the order
Edit a product from the layout
Key design decisions
Show what the customer will see
The builder is two phone previews: the menu with its categories, and the category that is open. What staff build is what customers get in the app, so they never have to guess.
One step at a time
Add product stays greyed out until the first category exists. The order of the work is shown by the interface, not explained in a manual.
Guidance where the work happens
While no panel is open, the right side shows a summary of the layout and a short guide in three steps. It disappears when there is work to do.
Products are reused, not copied
Products come from the product catalogue (PIM) and are added per category, so the same bowl can sit under both Lunch and Bowls without being created twice.
Simple styling with safe defaults
Each category card has a name, a text colour and a background colour with defaults filled in, or an image as background with one toggle.
Nothing gets lost
Changes save automatically, and “All layout changes saved!” confirms it. Sort order is changed by drag and drop, and a product can be edited from the layout itself.
Next steps
Ideas I noted for the product backlog, beyond this design:
- Visibility settingsShow a category or product only for a certain service type or time of day, such as lunch.
- Colour palettesChoose from a palette or a recommended colour combination instead of typing a hex code.
- SubcategoriesNot supported in this design, and an open question for the next round.
- App brandingA place to set up the start page and general branding, such as logo and default colours.
More of my responsibilities at Baemingo
At Baemingo, I had several responsibilities. Each one is its own case.