Interfaces that survive scan, tap and screen readers.
For teams that have screens or a rough flow, and words people have to read. We turn that into UI that works on a phone and a laptop, with visible focus and errors beside the field.
Front-end is the part someone touches. Contrast, target size, an H1 that carries the page, forms that name their errors. If a brand board exists, that board runs the page. Bar Boef sounds like the room, not a hospitality template. Red Flags and Dirty Seconds were built for a dim room: large type, one job per screen while the timer runs.
Screens or a rough flow, and the words visitors will read, in their language.
Work that is live
barboef.nl is the public voice of a borrelcafé, NL, with paths to parties, room hire and contact. Red Flags and Dirty Seconds are Expo UI for a group that will not read a manual. We do not publish heatmap numbers. What you see is the product on the screen.
Bar Boef
Public site for a borrelcafé in Haarlem, plus a CMS so the venue can update copy, events and images.
Screenshot of the live site, 25 August 2026.
Red Flags
Friends build ridiculous date profiles and vote on the loudest red flags. Product goal: an active round inside two minutes.
Screenshot of the live site, 25 August 2026.
Dirty Seconds
A 30 Seconds-style explain-and-guess game. Starting a round in under a minute is the success bar.
Screenshot of the live site, 25 August 2026.
What you get
Usable UI in React or React Native, in the user's language. Focus, contrast, errors next to the field, and states for empty, loading and failure. We follow a brand board when one exists. We write copy too if you need that, in the Dutch or English the visitor speaks.
How we start
Bring screens or a rough flow, plus the sentences that belong on the screen. First sprint: one path you can tap. Review on a real device, not only in the developer's browser. Copy or flow changes during the sprint get named with the effect on the price estimate.
When this fits
This fits when the design or the words already exist and building the UI is the job. A whole site including deploy lives with web. An app through to the store lives with mobile. The website check scores title, meta, headings and alt text if you already have a URL.
Ready to tell us what you need?
Send the screens or the flow. We come back with a price estimate for the UI. If you already have a live URL, get the website score.
Questions about this work
- Do you work from Figma?
- Yes, or from a rough flow on paper. We need the words in the user's language. A file without copy is a start, not yet a job.
- What about accessibility?
- We aim for WCAG 2.1 AA on public pages: contrast, focus, labels, errors that name recovery. A formal audit is in the delivery if we put it in the job.
- Can you write the copy as well?
- Yes, if you need that. Dutch and English as full peers. Jargon may stay in English. We do not invent claims or figures.
- Is this UI only, or the API too?
- UI only is possible. Often the API sits in the same project, as with Weekboodschappen. Say in the quote what already exists and what we should build.