Checks

The design is reviewed as you work. The Checks tab lists what would break, or read badly, in the running app — with a one-click fix where the fix is unambiguous.

Reading the panel

Findings are ordered with warnings first. Each names the screen and element it concerns, with two controls:

Go toSelects the element and switches to its screen.

FixApplies the correction as one undoable step. Only where the fix is certain.

IgnoreDismisses this finding on this element. Restore it later from the ignored section.

Warnings

Things that will misbehave in the app:

Unbounded flexAn element told to fill space inside something with no space to give — a runtime layout error.

Missing collectionA binding or action naming a collection this project does not have.

Broken actionA tap pointing at a screen that no longer exists.

Empty containerA container with nothing in it, occupying space and showing nothing.

Unknown colourA token that is not built in and not in your palette.

Unreachable screenA screen nothing navigates to — not the home screen, and not a tab root.

Dead endA screen with no way back and no onward action.

Duplicate namesTwo layers with the same name, which makes asking for one of them ambiguous.

Notes

Judgements rather than certainties, worded as risk because the design cannot know everything the app will hold:

Overflow riskA screen whose content is likely to exceed the device it is designed for.

Fixed heightA container sized smaller than its content plausibly needs.

ContrastText against a background below the WCAG 2.1 readable threshold.

Missing imageAn image with neither a source nor a binding.

Orphan inputA field with nothing on the screen that would submit it.

Ignoring a finding

Some checks are right in general and wrong for your screen — an orphan-input warning on a search field that submits as you type, for instance. Ignoring one hides it for that element only, and the rest of the check keeps working everywhere else.

Dismissals belong to the design

An ignored finding is stored with the document, not with your browser — so the judgement travels with the design and holds for anyone who opens it.

What checks are not

Checks describe the design as it stands. They are not a gate — you can export with findings open, because sometimes a screen is deliberately half-built. What they prevent is being surprised by something the design already knew.