The screen looks finished but the flow is not
Visual design started before anyone wrote the steps a person takes.
Creative studio
Interfaces people can finish using.
UI/UX at Nerix is practical. We map the journey, structure the information, and design screens that engineering can build. Research is sized to the project: interviews and testing when they will change a decision, not as a ritual. We design websites, apps, and the systems that keep later screens consistent.
Problems we help with
Every new feature invents a new style
Buttons, forms, and spacing drift because there is no shared system.
The enquiry dies in the form
Labels are unclear, errors are vague, or the page asks for too much.
Services and deliverables
What this engagement can include. The final scope is agreed per project.
User research
Focused interviews or reviews when a decision needs evidence.
User personas
Short portraits based on what you know about real customers, not fiction presented as data.
Customer journey mapping
The path from first contact to the task being done.
Information architecture
The map of pages, navigation, and labels.
Wireframing
Structure before colour, so the layout can be argued on its merits.
Interactive prototyping
A clickable flow for the paths that are easy to get wrong.
Website UI design
High-fidelity pages ready for build.
Mobile app UI design
Phone screens with states, not only the happy path.
Design systems
Components, type, and spacing for a product that will grow.
Usability testing support
A short test plan and notes from sessions you can run or we can facilitate.
UX audits
A review of an existing product with a prioritised list.
Accessibility reviews
Checks against practical barriers: contrast, labels, focus, and structure.
Conversion-focused redesign
Page changes aimed at a defined action, without a promised conversion rate.
Key benefits
Buildable design
Files are organised for the developer who will implement them.
States included
Empty, error, and loading views are designed, not invented in code.
A smaller decision set
We design the flows that matter instead of every imagined screen.
Shared language with engineering
Components in Figma match the way the interface will be built.
Tools and technologies
- Figma
- FigJam
- prototype testing
Our process
01
Frame the task
Who is using it, what they are trying to do, and what done looks like.
02
Structure
Sitemap or flow, then wireframes of the critical path.
03
Visual design
Interface, components, and the states around the path.
04
Support the build
We stay available while engineering implements the screens.
Relevant use cases
A product before development
Flows and a prototype that keep the first build small.
A website that does not convert interest
An audit and a redesign of the pages where people drop off.
A growing app
A design system so new screens stop looking unrelated.
Questions
Related services
- Website DevelopmentBusiness websites, landing pages, and web applications built to explain the offer and collect the right enquiries.
- Mobile App DevelopmentCross-platform and native-feeling apps for customers, bookings, and teams who work from a phone.
- Graphic DesignIdentity, campaign creative, and marketing collateral for businesses that need a consistent visual system.
- Custom SoftwareInternal tools, SaaS products, and integrations for workflows that spreadsheets and off-the-shelf apps no longer cover.
Discuss Your Project
Tell us about your ui/ux design needs and we will suggest a sensible starting scope.