INFI DISPLAY
UI design for every story

The whole setup is two surfaces talking to each other: the TV shows a code, INFI Connect claims it. Nothing is typed on the TV and no remote is needed past turning it on. The screen states its own code large enough to read from across a room, and INFI Connect never asks which position in a wall it is — a display is one screen.

This story is a subtraction. Everything that made a display a container for several screens leaves the UI: the 1/2/3/4 screen-count picker, the per-screen category tabs, the “SCR n” badges, the n-of-m counts, and dragging a category from one screen to another. Nothing is deleted below the surface — a single switch brings all of it back.

The operator picks a template, then turns three or four knobs — brand colour, logo, text size, what to show per item. They never pick a text colour, because contrast is the system's job, not theirs. Item images, descriptions, calories and Best Seller tags are read from the item record, so nothing on this screen asks for content that already exists.

The board has no menu of its own. It points at a menu, and the only decision the operator makes is what an unavailable item should look like — gone, or visibly struck. Everything else happens without them: a price edit, an 86, a new photo on the item record.

This is the only screen in the product whose user is the guest, not the operator. It answers one question from across a room — is mine ready — so it shows numbers at a size that works at eight metres and nothing else. No items, ever: the board is read by everybody standing in the room.

The operator is not in the store, and the screen cannot tell them anything. So the list is the product: every display, whether it is connected, and when it was last heard from. Two actions cover the incidents this story claims — refresh it, and make it identify itself so the right TV gets unplugged.

The failure this story exists to prevent is a blank TV above a queue. So the board keeps showing the last menu it received, forever if it has to, and never renders a network error where a guest can read it. Staff get a quiet signal that content may be stale; guests get a menu.

Merchants buy their own hardware, so the most valuable screen in this story is a list of model names with a verdict next to each. The hard constraint is whether the device can be kept awake indefinitely — a stick that lets a screensaver take the board is not a menu board, and the list has to say so before anybody buys one.

Nobody should discover the price of a screen on an invoice. The cost is stated in the confirm step, before the screen is paired, and the running total lives on the same strip as screen health. Releasing a screen mid-cycle keeps the seat for the rest of the period, which is said plainly rather than discovered next month.