WorkbenchField notes

Useful

Notes from the bench

Short practical tips we repeat most often. Take them and use them — even if you never work with us.

Illustrative photo: screen sketches and a phone on a terracotta tray by a window

Labels above fields, not inside

Placeholder text inside a field vanishes as soon as typing starts — and people forget what was asked. A label above stays visible, is read by screen readers and isn’t confused with an entered value.

An error message that helps

A good message says what happened, why, and what to do next — in human words. “Error 422” helps no one. “This email is already registered. Sign in?” does. Show it next to the field, not only at the top of the form.

Tap targets on phones

A finger isn’t a mouse. Interactive elements should be at least about 44 × 44 pixels with space between them. This matters most for unlabelled icons and links within text.

Empty states are a first impression

An empty list after sign-up is the moment someone decides whether to stay. Explain what will appear here and give one action to begin.

One thing, one name

If the menu says “Orders”, the button “Purchases” and the email “Your deals”, people will think they’re three different things. Keep a short product glossary and follow it in both languages.

Before submitting a store update

Check that screenshots match the new version, the change notes are updated, no new permissions appeared unexplained, and reviewer test access works. Store rules change — check official Apple and Google documentation.

Want to check this on your product?