Try That UI

Pattern library

Patterns for decisions that survive the handoff

This is a small public library of UI review patterns. A pattern here is a checklist for a kind of interface change: which states to look at, and which claim you should not make unless the screen actually supports it.

What a page in this library is

Each note is editorial guidance. It is written so a reviewer can hold a proposed change against a current screen and see whether the interaction is honest. It is not a component you install, and it is not a gallery of effects. Try That UI, the product, is the workspace where you do that comparison. These pages explain what to look for. They do not apply a pattern to your repository.

Use one when you already have a specific change in mind. Bring the current interface in as a URL or screenshot, put the proposal on Proposed, and walk the pattern's states before you keep or reject it. If the pattern says to inspect recovery, look at recovery. A polished default state is not the review.

Published

Reversible actions

When an action changes meaningful state and a real undo or recovery path exists, let people act and undo. Do not label the action reversible unless recovery restores the relevant data and the person can tell that it worked. Blocking confirmation is for the actions that cannot be safely undone.

That is the only published pattern. More notes will be added when they have been used in real reviews, not to fill out a catalog. If you are looking for a component to drop into an app, this library will not give you one. If you are looking for how to judge a recovery path before you implement it, start with the note above and the review workflow.

How this relates to the product

Inside a Try That UI review, Current stays the screen you supplied and Proposed can hold an isolated prototype of the treatment you are considering. The pattern tells you which states that prototype needs to show. The product still does not replay your application, and keeping the direction does not change your code. Read about the product if you want the boundary in one place, or the pattern feed if you want the published notes as a feed.

Questions

Is this a component library I can install?

No. These pages are review notes. They describe what to inspect in an interface change. They are not a package, a catalog download, or a claim that Try That UI ships those components into your app.

How many patterns are published?

One: reversible actions. More notes will be added only after they have been used in real reviews. The library does not list patterns that are not written yet.

How do I use a pattern with a review?

Bring the current screen into Try That UI, put the proposed change beside it, and check the pattern's states against that pair before you keep or reject the direction.