QRDER · Illustrative product design

Make the state clear before asking someone to act.

This story describes the interface shown in the existing design assets. It is not presented as a deployed client outcome or a claim of measured results.

Customer-facing QRDER restaurant menu with categories, items, and prices — Customer-facing menu example · sample names, details, and prices shown.

Problem

Customer and operator views can drift apart.

When the current state is hard to read, even a small menu or theme change becomes difficult to trust.

What the design shows

One menu, with explicit editing states.

The proposed system connects a customer-facing menu to theme selection, unpublished-change labels, preview, and operating context.

What it is designed to enable

A clearer review before publishing.

An operator can identify the applied theme, see that changes are still unpublished, and choose the next editing or review action.

The label before the button

Selected is not the same as live.

The theme library shows both “Applied Theme” and “Unpublished Changes.” The selected card exposes settings and editing controls; other cards keep preview and details available. That distinction is the useful part of the story.

Design shown01 / 03

CustomerStart with the menu people actually use

A readable customer-facing view makes the purpose of the system concrete.

QRDER theme library with Applied Theme and Unpublished Changes labels — Theme-library design showing explicit state labels and alternate controls.

QRDER dashboard with illustrative restaurant metrics — Operating-view design. Metrics and business details are illustrative, not reported results.

Your turn

What state is your unfinished thing in?

Find my first move See other finished work