The shared Ident.ink design checklist is published today, 12 November. It brings both 20-point lists into one review standard: clear typography, readable surfaces, consistent controls, useful feedback and restrained motion. Each check applies where it helps the task. Editors, dashboards and public or legal pages keep layouts appropriate to their work.
The full Ident B2B and Ident SaaS launch is scheduled for 13 November 2026 at 10:00 Europe/London. The main launch article is scheduled for the same time, following verified activation. Preparation, builds, tests and recovery checks run beforehand.
The design update
The first list explains the decisions behind readable and usable interfaces. The second is a practical cleanup checklist. They extend existing shared colours, spacing, loading states, keyboard focus and reduced-motion rules. Optional techniques such as staggered or shared-element transitions should be used only when they improve the task. Billing and access always wait for verified server state.
20 design terms: the practical checks
- Kerning: Check awkward letter pairs in large headings and logos. Prefer the font's normal kerning; avoid manual fixes to ordinary body copy.
- Optical centre: Visually centre icons and short labels inside their hit areas. Keep the actual control box, keyboard focus and pointer target aligned.
- Tabular numbers: Use equal-width digits for changing prices, counters, timers and comparable table columns. Keep the correct currency, precision and locale. Ordinary prose does not need this.
- Layout shift: Reserve space for images, payment fields, async results and loading placeholders. Loading or error text must not move a control beneath a user's pointer.
- Tracking: Adjust letter spacing sparingly for short display text. Avoid widely spaced body copy, forced uppercase paragraphs and changes that damage another script's shaping.
- Optimistic update: Use immediate feedback only for reversible changes with rollback and a clear failure state. Payments, billing, permissions, account activation and destructive actions require authoritative confirmation.
- x-height: Judge perceived text size and legibility at the actual rendered size, particularly for muted labels and dense tools. Matching font-size values alone does not establish consistency.
- Touch target: Aim for the existing 44px house control target on touch screens, with enough separation. Dense desktop editor controls need an appropriate touch alternative; enlarged invisible targets must not overlap.
- Leading: Give paragraphs comfortable line spacing and keep compact control labels readable. Review real multi-line text, zoom and translated copy.
- Origin-aware animation: If a menu, popover or panel animates, its motion should relate to its trigger and actual position. No animation is required to meet this check.
- OKLCH: Consider perceptual colour coordinates when deliberately deriving token variants. Keep existing hex/RGB tokens where they work; changing colour syntax is not a design improvement by itself. Verify the rendered contrast.
- Widow: Avoid isolated final words or stranded lines in important headings and short copy. Also inspect orphans at page/column breaks in print and export layouts. Prefer width/type adjustments over forced breaks in dynamic or translated text.
- Safe area: Keep fixed controls clear of device cutouts, home indicators, browser chrome, the on-screen keyboard and floating consent/language controls. Check real mobile layouts; use safe-area insets where relevant.
- Stagger: Use sequential reveals only when they clarify a group. Never delay access to information or controls, and do not add stagger merely for decoration. Respect reduced motion.
- Line length: Constrain long prose to a readable measure; roughly 45–80 characters is a starting point. The existing legal copy track uses 76ch. Tables, code and editor canvases need their own layout.
- Affordance: Links, buttons, inputs, draggable handles and disabled controls should communicate their purpose through familiar appearance and behaviour. Essential actions must also work without hover or dragging.
- Combobox: Use a searchable selector only when the choice set warrants it. Prefer a native select for simple choices. A custom combobox needs an accessible name, keyboard navigation, announced selection, Escape and correct focus behaviour. A plain search field is not automatically a combobox.
- Interruptible animation: New navigation, dismissal or repeated input must cancel or redirect motion safely. Do not queue stale animations, trap focus or block interaction until an effect finishes.
- Progressive disclosure: Put advanced settings and secondary detail behind clearly labelled sections when useful. Keep prices, commitments, consent, errors and primary actions visible before the relevant decision.
- Shared element transition: Optional: use a transition between related views only if it improves orientation. Preserve navigation, focus, scroll and history, provide a normal navigation fallback, and respect reduced motion.
20 checks for cleaner interfaces
- Delete filler badges: Remove decorative chips that repeat a heading or invent importance. Keep meaningful availability, security, health and status indicators.
- Drop redundant labels: Remove labels that repeat nearby content without helping comprehension. Preserve input labels, accessible names and necessary units.
- Unitalicize random words: Use emphasis for meaning, not arbitrary visual variety. Preserve semantic emphasis and correctly styled quotations/titles.
- Mono only where needed: Reserve monospace for code, identifiers and technical values where useful. Ordinary navigation, help text and business prose use the shared text family.
- Use a design system: Reuse established tokens, spacing, type scales, buttons, inputs, dialogs and feedback states. Extend the shared component when appropriate instead of adding page-specific overrides.
- Show the actual product: Prefer a useful real interface or a clearly labelled illustrative view. Never invent customer activity, revenue, live metrics or working capabilities for a mockup. Protect private data in screenshots.
- Enlarge the main feature: Give the working tool or key information the space it needs. Reduce oversized marketing headers and empty space that push the task below the fold.
- Group with spacing: Establish a clear relationship between a label, control, help and action. Use spacing before adding boxes, dividers or another card.
- Make headlines specific: State the task, product or outcome in plain language. Replace generic promotional wording where it obscures what the page does.
What the 13 November launch covers
Ident SaaS is the self-service route: choose supported tools, review scope and limits, choose a three- or twelve-month term, then pay through Ident Secure Pay on Ident.ink. Payment comes before account creation. The one-use invitation goes to the payment email, and that email must be used for the account. Existing customers can claim a paid purchase with the matching verified email.
All 20 non-hosting products are already available through the staged rollout within their displayed limits. Bot hosting and server hosting require a reviewed offer from an Ident administrator. Customers complete their own DNS ownership, merchant verification, recipient onboarding and other provider checks for relevant tools. Those checks do not turn normal SaaS purchases into support-only offers.
The fixed-price bundle has one £5/month workspace base plus the selected product rates. £5 is a minimum, not the price of every product. Three- and twelve-month terms can be paid monthly or upfront; the complete commitment is shown before agreement and terms do not renew automatically. IdentDB keeps separate actual-usage billing at £6 per 2 decimal GB-month of active document JSON, with a chosen cap and explicit saved-card billing consent.
Ident B2B is the separately agreed business-contract route. The planned launch covers applications, business verification, an administrator-approved scope, required signatures and controlled access to the contracted services. A normal SaaS payment does not grant traditional B2B contract rights. A conversation, application or incomplete signature is not an activated business contract. The launch report will explain the verified plans, limits and customer steps in full.
Where to start
Choose SaaS products, read the current rollout information, or contact Support for an existing account or a hosting enquiry.
The launch article will appear in News at 10:00 Europe/London on 13 November with the verified release scope. Current rollout information distinguishes what is already live from what is scheduled.