Product UI

How our products look, behave and talk. One standard for every screen, so a button looks and works the same in every app we build.

The standard: shadcn/ui, our colours and font

Layout, components and interaction follow shadcn/ui (new-york style): its sizes, spacing, radii, states and component anatomy. Colour and type stay ours: the brand tokens and Murecho. One deviation, from our design philosophy: no shadows, elevation is a 1px border.

Why shadcn/ui: it is built on Tailwind like our apps, it is monochrome like our chrome, its behaviour (keyboard, focus, Escape) follows the WAI-ARIA patterns, and it is the look people already know from tools like Vercel and Supabase.

In code: build with the shared component library of the app (in Odoo MCP Pro: templates/_ui.html), never with hand-written button or badge classes. Look components up with the shadcn MCP server; translate, never install React files into a Jinja or Odoo app.

Page types

Every screen is one of five types. Pick the type first; the layout follows.

List

A title, one primary action top right, one table. The whole row opens the thing. One status column. Example: Odoo instances.

Overview

One thing at a glance: title, its status and an Open action, then a card of rows (label, value, at most one action per row). Example: an Odoo instance.

Settings

Sections with a short heading, each a card of rows. Change a value in place on its own row. Destructive actions last, folded under Danger zone.

Flow

Creating something that takes a form with checks gets its own page (/new): a back link, one title, the form. The choice of how to add comes before it, in the menu on the button.

Empty

One muted line and at most one action, inside a dashed border. No illustration needed, no explanation of the feature.

Which element, when

Element Use it for Not for
Primary button The page's one main action (Add Odoo instance, Save). Two on one screen; secondary actions.
Outline button Every other action on the page. The main action.
Ghost button An action inside a row or a table cell. Standalone actions.
Destructive button Remove, delete, cancel for good; only in the danger zone, always with a confirmation. Anything that can be undone.
Badge The status of one thing, in one or two words. Messages, explanations, counts that need a sentence.
Alert A message about this page or the last action: saved, failed, needs attention. Permanent explanations of how the product works.
Table A list of things of one kind. The properties of one thing.
Card with rows The properties of one thing, each with at most one action. A list of many things.
Dialog One short step that is not an edit of a value on screen: confirm, pick a plan, name a new thing. Flows with checks; editing a value already shown.
In place Changing a value already on screen (rename, change an address), on its own row. Creating something new.
Fold Secondary sections: recent errors, danger zone, advanced options. The main content or the main action.
Switch On or off with immediate effect. A choice inside a form that is saved later (use a checkbox).

Colour means status

Green: works. Amber: needs the user. Red: broken. Grey: off or not started. Purple (accent) is for the primary action and links, never for a status. Everything else is neutral.

Interaction rules

  1. One action per goal per screen. If a banner and a button start the same thing, keep one.
  2. A click on an action opens the action, not a page that asks for another click.
  3. Say each fact once per screen.
  4. Show state, not options: status is visible on the list, without opening anything.
  5. Silent when healthy: only show what the user has to act on.
  6. Never unfold a form or a panel below a list; the eye stays at the button.
  7. One kind of thing has one list component, reused wherever it is listed.
  8. Done means clicked: do every action you touched and judge the screen right after the click, on desktop and on a phone.
  9. Several ways to do one action (connect an existing one or create a new one) are a menu on the action's button, never a page that only asks which way. A way that is not available stays in the menu, disabled, with the reason.

Speed

A screen feels right when it answers at once. These numbers are the limit, measured on a mid-range phone (4x CPU slowdown, slow 4G).

  1. Every click answers visibly within 100 ms: the button presses, the row highlights, the dialog opens. The next frame is on screen within 200 ms (INP).
  2. If loading takes longer than 300 ms, show a skeleton shaped like what is coming: the same rows, cards and columns, muted. Below that, no skeleton, it only flashes. No spinner over a whole page.
  3. If something takes longer than 10 seconds, say what is happening and how far along it is: "Installing apps, 3 of 7".
  4. Motion runs at 60 fps and lasts 150 to 200 ms. Animate only transform and opacity. With prefers-reduced-motion: no motion.
  5. No task blocks the page for longer than 50 ms. A list of hundreds of rows paginates or virtualises.

Writing for the interface

Product UI follows our tone of voice, tighter: the reader is in the middle of a task. Product screens are in English.

  • Sentence case everywhere: titles, buttons, labels, headings.
  • Buttons are a verb and the thing: "Add Odoo instance", "Remove", "Back up now". Never "Click here" or a bare "OK".
  • Write small. Say what to do, not how the system works. Title one line, no explainer under it; help text one sentence at most. Cut your first draft in half. If the screen still needs more words, the screen is wrong, not the copy.
  • Status words name a state, short: Connected, No key, Off, Running, Stopped, Down.
  • Errors say what happened and what to do, in one or two sentences, without codes: "Our server did not answer. Try again in a minute."
  • Confirmations: the title asks the question with the thing ("Remove this Odoo instance?"), the body says the consequence, the button repeats the verb ("Remove").
  • Time and numbers as people read them: "2 Oct, 03:00 UTC", "3 of 50 calls today".
  • No em dashes. No buzzwords. Read new copy back once for AI tells before shipping.

Fixed terms

Say Means Never
Odoo instance One Odoo (an address and a database) a workspace connects to or we host. an Odoo, Odoos, database, connection
Odoo The product or the app itself: "Open Odoo", "Apps in Odoo". the thing a user adds
Server Carries Odoo instances. Ours: "Pantalytics server" (shared or yours). The rest: "Other hosting". host, machine, VM
Workspace The team space that owns Odoo instances, members and billing. team, organisation, tenant
Member, Administrator A person in a workspace, and the role that may change things. user (as a role name), owner
AI connector The link between an AI client (Claude, ChatGPT) and Odoo MCP Pro. integration, plugin
Key A member's own API key on an Odoo instance. token, credential, password (for an API key)
Agent An AI identity inside Odoo: it runs as the person who asks, or as a dedicated user with its own rights. bot, assistant (as a product name), AI user

Example

Don'tAdd Odoo
DoAdd Odoo instance
Don'tOur servers could not process your request (error 503). Please contact support if the issue persists.
DoOur server did not answer. Try again in a minute.

Less is more: the lazy user

AI adds by default: another title, a subtitle, a help paragraph, a second button, one more feature. We remove. Every screen answers "where do I tap?" in one glance, and the answer is an action.

The gate before ship is a lazy user: half drunk, or four years old. It sees only a screenshot, at desktop and phone width, and a one-line task. It names its first tap. A wrong tap, two candidates, or a sentence it had to read means the screen is wrong, not the user. What it ignored and no task needed, we delete.

Inside Odoo

Inside an Odoo module the user lives in Odoo all day, so our screens look and behave like Sales and CRM. Odoo's frame, our restraint: our taste shows in what we leave out, not in how Odoo is painted.

Zone What Rule
Native Navbar, app menu, breadcrumbs, control panel, search, chatter, settings layout, theme, phone shell. Never restyle, patch or replace.
Restrained Forms, lists, kanban, wizards, fields, buttons, badges, settings content. Odoo's widgets, our rules: one primary action, colour means status, short copy, fewest fields.
Ours Screens Odoo has no pattern for, such as an inbox or a setup checklist. Our layout rules, built from Odoo's parts and colours, inside Odoo's frame.

Not in the Odoo backend: our accent, Murecho, shadcn/ui components or sentence-case labels. Labels follow Odoo's Title Case next to Odoo's own.

How Odoo's interface is built, screen by screen, with annotated screenshots: Odoo UI.

The full rules for AI and developers: the pantalytics-odoo-ui skill.

Before you ship

  • The page is one of the five types, with one primary action.
  • Every element is used for what the table above says.
  • Colour only for status; accent only for the primary action and links.
  • Copy: sentence case, verb plus thing, fixed terms, no explainers, nothing that could be shorter.
  • Every touched action clicked and judged right after the click, at desktop and 390px.
  • The lazy user passes: one screenshot and a one-line task, first tap right without reading a sentence.