UX/UI design for web apps and dashboards, organized around the tasks people do in them
We design the screens people use to get work done in a web product: customer portals, SaaS and CRM dashboards, admin tools, the screens around AI features, and the sign-up, onboarding and setup flows that lead into them. For a live product, we can review it and redesign the few screens that cause the most trouble, or refine it one screen at a time inside its design system. For a new product, we prototype it so its open questions come up before development. Your developers build from the Figma file, or our developers make the changes in your codebase.
Norml is responsible for how the product works on screen: which tasks come first, where each one starts, what every screen shows in each state, and the Figma file the build follows. Product rules and data stay with your team, and back-end work is scoped on its own.
What web app and dashboard UX/UI design covers
Work starts with who uses the product and which tasks they repeat, because those tasks decide which screens change first. A project can be one flow in a live app, a set of dashboard screens or the first version of a new product.
Review of the live productWe sign in as each type of user and work through the main tasks on a desktop and a phone. Typical findings are tables that are hard to scan, empty screens that leave people guessing, actions with no visible result and navigation that hides frequent tasks. Each finding names the screen, the problem and a suggested change, and the list is ranked by how often the task comes up and how much the problem slows people down.
01
Roles, tasks and navigationWe map who uses the product and what each role does most: customers and the staff who serve them, buyers and the businesses listed on a platform, or the person who sets up a system and the person who uses it every day. Navigation is arranged around those tasks, and each role's journey is reviewed and designed separately.
02
Tables, dashboards and dense dataFor screens that hold many records, we settle what each screen is for, which columns matter most, how rows are grouped and sorted, which filters stay applied and which actions sit on each row. Summary views put the figures people check daily at the top, and wide tables get a layout planned for smaller screens.
03
Every state of each screenScreens are designed in the states people actually meet: empty, loading, partial, error, success and no access. A first-use screen explains what to do next. Multi-step flows, comparisons, calculators and dialogs get every step drawn, and screens with many options reveal them in stages while keeping a summary of the choices made so far. Features that generate content with AI get states for waiting and for failed or partial results, with controls to edit, retry or keep a result.
04
Sign-up, onboarding and setup flowsLong forms are split into steps by topic, with progress shown, optional fields marked as optional, labels that say what to enter, and validation messages that explain how to fix an entry. The last screen confirms what was saved and says what comes next. The same approach applies to setup and maintenance tools for products that connect to hardware.
05
Prototypes before developmentWhen a product exists only as requirements or a demo, we wireframe its main workflows and link them into a clickable prototype. Walking through it with your team and developer brings out missing steps, conflicting rules and unclear terms, which we list as questions for the product owner before visual design and development start.
06
Responsive screens and a component systemScreens are designed at desktop and phone widths for use in a browser, and contrast, text size and touch-target size are checked on each one. Buttons, fields, tables and navigation become Figma components with variants and Auto Layout, with color, type and spacing kept as variables and styles, so new screens are assembled from the same parts.
07
Handoff or implementationYour developers receive the Figma file with notes on interactions, error messages and edge cases, plus exported icons and images, and we walk them through it. When our developers build the changes instead, they work from the same file and your existing code.
Shows an operational web app we designed and built: in DoorKnockPro, field teams filter properties by several parameters inside zones they draw on a map, open a route for each campaign and record what happened at each door. Qualified leads go to the CRM.
Shows our interface design for large sets of records: for Nasdaq Private Market we designed the directory interface, with navigation and search across thousands of company pages, each laying out financial data in a scannable format.
Shows a multi-step sign-up from our work for a pet health platform: registration forms collect each pet's species, breed, age and health details without one long form, and automated email and SMS surveys reach pet parents every few weeks afterwards.
Shows our structure-first step on an AI company's website: for a genomics platform we mapped over 50 potential pages, wireframed the five it needed first and worked with its marketing team on messaging for US clinicians.
Access to the productA test or staging account for each role, with sample data, shared by invitation. If the product isn't built yet, we work from its requirements, a demo or screenshots instead.
01
The tasks that matter mostWhich tasks each role does most often, the questions your support team hears again and again, and any analytics or session recordings you have. They decide which flows we look at first.
02
Design files and specsThe current Figma file, design system or component library, brand guidelines, and any written spec that says what each screen is for.
03
Product rulesStatuses, permissions, plan limits, validation rules and edge cases, or the person who knows them. Screens follow the rules you approve, and gaps we find go back to you as questions.
04
Who builds the screensWhether your developers or ours build the designs. For your team, tell us the framework and component library they use and who reviews the handoff. For ours, we need repository access by invitation and the checks each change must pass.
05
One product ownerOne person who answers product questions, approves each round of designs and gathers comments from the rest of your team in one place.
06
How a web app UX/UI project runs
[Agree roles, tasks and screens]
We list who uses the product, their main tasks and the screens involved, and agree which flows the work covers first.
Step 01
[Review or map the flows]
For a live product we work through each task with test accounts and rank the problems we find. For a new product we map the flows from its requirements and list the open questions. A review-only project ends here, with the ranked findings.
Step 02
[Wireframe and prototype]
The chosen flows become wireframes and a clickable prototype, which your team and developer review before visual design starts.
Step 03
[Design screens and states]
High-fidelity screens are designed at each agreed width, with their empty, loading, error and success states, built from shared components.
Step 04
[Pass on the file or build the screens]
Your developers get the Figma file and a walkthrough, or our developers build the changes and send each one for review.
Step 05
[Review the built screens by role]
Before release we sign in as each role and compare the built screens with their designs at every agreed width, including the empty, error and no-access states. Developers get each difference with the screen, the state and the change needed.
No account layer between you and them. These are the Norml specialists this work runs through.
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Questions about web app and dashboard UX/UI design
Can you redesign a few screens rather than the whole product?
Yes. We pick the flow that causes the most trouble, redesign the screens it passes through and leave the rest of the product as it is. The new screens reuse your existing components where they fit, so they sit comfortably next to the screens we don't touch.
Can we start with a review and decide on the redesign later?
Yes. The review is useful on its own: you receive the findings in priority order, with screenshots, and decide what to change. A redesign of the agreed findings can follow as a separate scope, with us or with your own designers.
Will you work inside our existing design system?
Yes. Screens are built with your tokens and components, and any written screen specs are our reference for what each screen should do. When a screen needs something the system lacks, we propose the new component and agree it with you before using it.
Can your developers make the changes in our front-end code?
Yes, when the front end uses a framework our developers work in, such as React. They reuse the components already in the repository, keep each change to a single screen so it is easy to review, and run your type checks, tests and interface checks before you see it. Back-end changes are scoped separately.
Do you need to understand our data to design the screens?
Yes, enough to know what each field means and which decisions it supports. We ask for real or realistic sample records early, because placeholder data hides problems such as long names, empty fields and very large numbers, and we review the screens with that data before handoff.
Can you design a customer portal and the public website together?
Yes. The signed-in area and the public pages are designed from one set of components, so navigation, type and buttons stay consistent when a customer signs in. The portal screens cover the states each kind of customer meets, such as a pending quote or an unpaid invoice, while sign-in, payments and permissions follow the rules your developers implement.
We already have a working demo. How do you use it?
As the reference for business rules and the order of steps. The screens are designed independently, so the result is not a restyled copy of the demo, and anything the demo leaves unclear is raised with your product owner before the screens are final.
Is the prototype working software?
No. It's a clickable Figma model of the main workflows, made to check the steps and rules before anything is built. Development is planned once the prototype and its open questions are settled, with your developers or ours.
Do you design the screens of AI features?
Yes. We design where users give input, wait for a result, compare or edit what was generated and decide what to keep. Drafts and saved results look different, and when an action uses credits or has a limit, the screen says so before the user commits. Model behavior and quality thresholds stay with your engineering team.
Can you compare our product with competitors?
Yes, using what those products show publicly: their websites, help pages, public demos and sign-up screens up to the point where an account is needed. We compare how each handles the same journey and turn the differences into recommendations for your product. We don't record other companies' apps through personal accounts or capture their identity checks and payment screens.
Does this include native apps, back-end work or accessibility certification?
Apps people use mainly on a phone, whether native or progressive web apps, are scoped as mobile app design; this work covers web products used in a browser on desktop and phone. Back-end logic, data models and new features built end to end belong to a web app development project, and formal accessibility certification is not included. We also don't promise a completion or conversion figure. Where analytics exist, we record a baseline for the steps we change so you can compare them after release.
Read the rest of our case studies
Find out who each product was for, the problem it started with and which part of the work was ours.