Our UI/UX design services cover web apps, mobile apps, portals and dashboards, from the first user interview to the screens your developers build. The people who design your screens work in the same team as the people who build them, so nothing is lost at handoff.
Telemeds+ designed from research to release · Clinic site with an ADA check · 5.0 on Clutch
UX AND UI
UI/UX design services research how people use a product, then design its structure, flows and screens. UX design covers research, information architecture, user flows, wireframes and testing; UI design covers the visual screens and the component library developers build from. Metwaves designs web and mobile apps with the same team that builds them, and has shipped design work in healthcare and fintech.
What the product does, and in what order
Who uses this, for what, and where do they get stuck?
Research notes, personasWhat does the product hold, and where does each thing live?
IA mapWhat are the steps for each task, and who does each one?
Flow diagramsDoes the layout work before it is styled?
Wireframes, clickable prototypeHow each screen looks and behaves
How does each screen look, on every device?
Final screensHow do buttons, forms and states look and behave everywhere?
Component library, design tokensWHEN TO CALL US
These are the sentences that usually start a design project with us.
SERVICES
Six services you can buy together or on their own. Each one ends with something you can open, review and keep.
Interviews, analytics and support tickets turned into a ranked list of problems, each with the evidence behind it. For a live product, the audit says what to fix first and what to leave alone.
You keepResearch notes and a ranked problem list
What the product holds, organised by role, and a flow diagram for every task, so nobody argues about screens before the structure is agreed.
You keepAn IA map and flow diagrams
Low-fidelity screens that settle layout and content before anyone spends time on colour, reviewed with you page by page.
You keepWireframes for every key screen
Clickable journeys put in front of the people who will use them, before code. For prototype then MVP, see software prototyping.
You keepA clickable prototype and the feedback on it
Final screens, plus the colours, type, spacing and components behind them, so new screens match the old ones without a designer in every sprint.
You keepFinal screens and a component library
Contrast, focus order, text size and labels checked before handoff, with every state a developer needs: empty, loading, error and success.
You keepSpecs and states, in the sprint that builds them
The flow diagrams drawn in design are reused through the build: developers build from them, and testers write their test cases from them.
The design files, prototypes, flow diagrams and the component library are yours, in a tool your team can open. Nothing is locked in our accounts.
Healthcare products serve several roles under privacy rules, often on a phone, often in a hurry. We have designed and built two that are live as case studies: the Telemeds+ telemedicine app and an urgent care clinic's website. See healthcare software development for the build side.
Telemeds+ has patients, doctors and administrators, each with their own dashboard and tasks. We designed each role's flows separately before any screen.
We designed for use at home, on the go and in the clinic, and decided which features matter most on a tablet and on a phone.
HIPAA controls (encryption, access controls, audit trails, encrypted video and messages) decide what each screen shows and to whom.
For the urgent care clinic, booking and the list of treated conditions are one tap from every page, built for a phone held in one hand.
The clinic site had an ADA accessibility check before launch. In healthcare, retrofitting it later costs far more.
CASE STUDY
A physician who owns two urgent care clinics in Virginia came to us with an idea for a telemedicine app and no written brief. He asked us to research, wireframe and test the idea before building it.
Our business analyst and technical lead interviewed the client and his team, built proto personas, mapped the information architecture and drew a flow diagram for every function. We walked the stakeholders through low-fidelity wireframes page by page, revised them, then handed over to visual design and development. Testers wrote their test cases from the same flow diagrams.
We agree the numbers before we design, then measure the same numbers after release.
Each result is reported in the project's case study.
Five steps. You review the result of each before the next one starts.
Interviews with you and your users, a look at analytics and support tickets, and the numbers we will measure after release.
Everything the product holds, organised by role, and a flow diagram for each task.
Low-fidelity screens walked through with your stakeholders, one page at a time, then revised.
The key journeys linked into a prototype, put in front of the people who will use them.
Final screens, a component library and the states developers need, handed to the team that builds them.
Design is priced by the hour, as a fixed price per phase, or as a monthly retainer. We prefer a fixed price for the design phase, so you know the cost before you start. These factors move it most.
A few screens for one role is a different job from a product with patients, doctors and administrators.
A review of analytics and support tickets is quick; interviews and tests with real users take longer.
Web, iOS and Android each have their own conventions, so each adds layouts and states.
A component library costs more up front and less on every screen after it.
Built in from the first wireframe it costs little; retrofitted later it costs far more.
A brand guide and real content to design with save rounds of revision.
Buy design on its own, or design and build with one team.

Research, flows, wireframes and a prototype for a new product or a redesign, quoted after the first call.

A fixed design phase, then a build estimate for web or mobile development by the same team.

Design capacity inside your own sprints, monthly.

New screens and fixes on a live product, paid for the hours used.
STANDARDS
Each platform has its own conventions. Following them makes an app feel familiar on the first tap.
Web apps and portals
iPhone and iPad apps
Android apps
Every platform
You get the design files in a tool your team can open, and they are yours.
CHOOSING A PARTNER
Signs that separate a team that ships products from one that only makes screenshots.
Design is the start. These services take it to release.
QUESTIONS & ANSWERS
Straight answers on cost, timelines, ownership and healthcare design. If you don't see an answer to your question, you can send us a message from our contact form.
We do. We designed and built Telemeds+, a telemedicine app with patient, doctor and administrator roles and HIPAA controls, and a booking-first website for an urgent care clinic that had an ADA accessibility check before launch. Healthcare design has to handle several roles, privacy rules and accessibility from the first wireframe.
Design is priced by the hour, as a fixed price per phase, or as a monthly retainer. The number of screens and user roles, the depth of research, the platforms (web, iOS, Android) and whether you need a design system move the price most. We quote a fixed price for the design phase after a first call.
Ask to see wireframes and the shipped product, ask who builds what they design, ask how they test, and check that you will own the files. Working hours that overlap with your team matter more than the firm's address.
We will not rank our competitors. Use the good signs and warning signs on this page to judge any firm, including us.
It depends on the number of screens and roles and how much research is needed. We give you dated stages after the first call, with a review at the end of each.
You do: the design files, prototypes, flow diagrams and the component library.
Often, yes. A UX audit ranks the problems by impact and effort, and many fixes are changes to existing screens rather than a rebuild.
UX design decides what the product does and in what order. UI design decides how each screen looks and behaves. Most projects need both.
Yes. WCAG 2.2 level AA is our design target: contrast, text size, focus order, screen reader labels and error messages that say how to fix the problem. The urgent care clinic site had an ADA accessibility check before launch.
Discover IT Industry Insights and Technology Trends
Support for .NET 8 and .NET 9 ended on November 10, 2026. What that means for apps still on them, how risky it is, and how to plan the move to .NET 10.
Learn More >Nine AI agent development firms a small or mid-sized business can shortlist, with Clutch figures, minimum budgets and the weaknesses their own clients name. Published by Metwaves, which is not ranked.
Learn More >An architecture review of the four big enterprise AI agent platforms: where each one reasons, acts, finds its data and connects to outside agents, what it costs, and when a custom build is the better choice.
Learn More >
Let us help you with free analysis & estimate.
Our product expert will contact you within 12 hours.