Interface design that survives the handover Websites, dashboards and mobile apps
Web design and interface work built on real content, never placeholder text. You get a system of tokens and components that the build uses directly, across websites, dashboards and mobile apps.
What the work covers
Every item below is part of the service rather than an add-on discovered later. Anything that falls outside it is named in the written scope before the work starts.
Web and marketing site design
Layouts designed against the content that will really exist, at every screen size.
Dashboard and product UI
Dense, data-heavy interfaces where clarity matters more than decoration.
Mobile app UI design
Native-feeling interfaces for iOS and Android, designed for thumbs and interruption.
Design systems
Tokens, components and states, so your tenth screen looks as considered as your first.
Accessible by default
Contrast, focus order and target sizes get decided during design, while they are still cheap to change.
Build-ready handover
Design delivered so developers can implement it without reinterpreting it.
How the work runs
Four phases, in this order, on every engagement. No stage begins before the previous one has produced something you have seen and agreed to.
Understand
Who uses it, what they are trying to finish, and where the current design gets in the way.
Structure
Journeys and hierarchy first, on real content, long before any visual polish.
Design
Interface and system built together, then tested at the sizes people really use.
Hand over
Tokens, components and states documented, with the build to match.
UI/UX Design questions
The questions that come up before committing to this work. If yours is not here, ask it on a first call. That call exists for exactly this.
Do I need a designer, or can I use a template?
For a simple site with conventional content, a template is honestly the right call. It stops being the right call once your content refuses to fit it, once the interface carries real complexity like a dashboard or a store, or once accessibility and performance start to matter. Past that point you spend more fighting the template than design would have cost you.
What does a website redesign actually involve?
Less visual work and more structural work than most people expect. The valuable part is deciding what the site has to do, which content earns its place, and how the pages relate to each other. Skip that and you get a site that looks newer and performs exactly the same.
Do you design mobile apps as well as websites?
Yes: mobile app interfaces, product dashboards and marketing sites. Viby-Z covered all three at once, the public platform, the organiser dashboard and the mobile app.
Is accessibility part of design or development?
Both, though it is far cheaper in design. Contrast, focus order, target sizes and heading hierarchy are all design decisions. Settling them on the canvas costs nothing. Retrofitting them after a build costs plenty, and the result is usually worse.
What do I get at handover?
A design system, not a folder of flat mockups. Tokens for colour, type and spacing, components with all their states, and the rules for how they go together.
Often bought alongside
Most projects use more than one of these. They are listed separately because the work is genuinely different, not because they are sold separately.
Build something that earns its keep
Tell us what the site has to do. The searches it needs to win, the customers it needs to convert, and how your team works day to day. You get a straight answer on whether it is a fit, and a written scope before anything starts.
- Senior-led from first call to launch
- Written scope before any build starts
- Built to WCAG 2.2 AA and tested
- Clients in Morocco, France, Oman and beyond