ERIKSLAIERsoftware workshop · Dnipro
Українська

Mon–Fri 09:00–18:00
Europe/Kyiv

Enquiry
Illustrative photo: light that sets the orderLight that sets the order · illustration

ERIKSLAIER Design

Design

Interfaces you can build

UI/UX in the workshop isn’t pretty pictures for a deck. It’s decisions a developer can implement without guessing and a person can use without instructions.

Flow first, pixels later

What a person wants to do and what stops them. Screens appear once the path is clear.

We draw every state

Empty list, network error, a very long name, a zero balance. If a state isn’t in the layout, a developer will invent it at 2 a.m.

Copy is design

Labels, buttons and errors are written with the layout. “OK” and “Error” aren’t copy.

Accessibility from the start

Contrast, tap target size and focus order go in before development, not patched afterwards.

Components, not pictures

We build a small system of buttons, fields and cards so new screens assemble quickly and consistently.

Illustrative photo of an architectural detail

If a state isn’t in the layout, a developer will invent it at 2 a.m.

ERIKSLAIER

An interface review in a few days

If the product is live but something feels off, we start with a review. We walk key flows at three screen widths, with keyboard and large font, and read all the copy. You get a list of concrete observations with priorities.

Example observation

Basket → “Checkout”. The button is disabled with no explanation when no delivery method is chosen. Suggestion: show a hint by the field and keep the button active with validation on press.

Illustrative, not from a real project.