Services · UI & UX Design
Research, information architecture, wireframes and interface design in Figma, built as a design system your developers can actually ship. We test with real users, so design decisions get validated instead of argued about.
You own the code and IP Weekly demos Reply within one business day
OlDevs is a full-stack technology studio in Vancouver, British Columbia that designs the interfaces and user experience of web, mobile and internal software.The work covers discovery and user research, information architecture, user flows, wireframes, interface design in Figma, design systems, clickable prototypes and usability testing. Accessibility to WCAG 2.2 AA is designed in from the first wireframe rather than patched on after launch, and every screen is handed to developers with tokens, states and specs documented. Clients own all designs, source files and IP.
Key facts
Product and interface design
We interview the people who will actually use the product, review your analytics and support tickets, and map the tasks they are trying to finish. That produces a short list of problems worth designing for, agreed with you before any screen is drawn.
Navigation, labelling and content structure come first, then flows and journey maps for each important task. Getting the structure right is what stops a product from becoming a pile of screens that nobody can find their way through.
Wireframes settle layout and hierarchy, then visual design applies your brand: type scale, colour, spacing, imagery and tone. If you have brand guidelines we work inside them. If you do not, we build the rules the product needs and document them.
We build the interface as reusable components in Figma, with variables for colour, type and spacing plus documented states and rules for use. One library keeps every screen consistent and makes the next feature quicker to design and to build.
Clickable prototypes let people try a real flow before any code exists. We run moderated sessions, watch where they hesitate or misread a label, and change the design based on what happened rather than on whose opinion carried the meeting.
Contrast, focus order, target sizes, labels and keyboard paths are decided while we design, to WCAG 2.2 AA. Handoff includes redlines, tokens, empty and error states, responsive behaviour and a walkthrough with the developers who will build it.
Process
Discovery
A kickoff to agree goals, users and constraints, then interviews, a review of your analytics and support data, and a look at the products your users compare you to. The output is a short brief everyone signs off before design starts.
Structure
Information architecture, user flows and journey maps for the tasks that matter most, then low fidelity wireframes. Changes are cheap at this stage and expensive later, so this is where the arguments get settled.
Interface design
Your brand applied to the agreed structure and built as a Figma component library with tokens, states and responsive rules. You see a working demo every week and can comment directly on the files.
Validation
Clickable prototypes tested with people who match your users, plus a review of every screen against WCAG 2.2 AA. Findings become a prioritised list of changes, and the designs are revised before anything reaches a developer.
Handoff and support
Specs, tokens, assets and a walkthrough for the build team, then design support through development and QA so what ships matches what was approved. Every file, account and IP right is yours. Request a quote to begin.
How we work
Every project starts by finding out what users are actually trying to do. Research notes, analytics themes and support tickets are written up in plain language, so the whole team is working from the same facts instead of competing hunches.
When two directions both look reasonable, we prototype both and put them in front of people who match your users. A short round of testing settles the question faster than another meeting, and the result is recorded so it does not get reopened later.
WCAG 2.2 AA shapes the design from the first wireframe: colour contrast, focus states, target sizes, error messaging and keyboard paths. Designing for it costs a fraction of retrofitting it once the product is live and the code has hardened.
For a product already in use, we run a heuristic and accessibility audit, review analytics and session data, then propose changes in priority order. Most teams get more value from a sequence of small, measurable releases than from one risky rebuild.
Designers and developers sit in one accountable team here, so files are structured the way engineers consume them: named components, tokens that map to code, documented states, responsive rules and a walkthrough before the sprint starts.
Layouts are designed to survive longer strings and different reading patterns, so English and French content sit in the same components without breaking. We work in both languages when the project calls for it.
Who it's for
Customer platforms and internal tools where the design has to fit existing brand rules, security review and a roadmap already in flight. We work alongside your product and engineering teams rather than around them.
Public facing services with mixed audiences and firm accessibility obligations. WCAG 2.2 AA conformance and bilingual English and French content are treated as normal requirements, not as extras bolted on at the end.
One design system applied across every location, so head office keeps control of the brand while each location gets the pages, forms and local details it needs without a designer redrawing the same screen each time.
Founders who need a product real people can use, designed quickly enough to test with customers and structured well enough that the first round of growth does not force a rebuild.
1 week
Between working design demos
5 to 8
Usability testers per round
100%
Screens handed off with documented states
FAQ
UX design is structure and behaviour: who the user is, what they are trying to finish, how the flow works and where it fails. UI design is the surface they touch: layout, type, colour, states and motion. Both are needed. A polished interface over a broken flow still frustrates people.
Yes. A large part of our design work is on live products. We start with an audit of the current experience, the analytics and the accessibility, then propose changes in priority order so improvements ship in small releases instead of one large rebuild that puts the business at risk.
A Figma file with the full component library, tokens and documented states, screens for every flow at each breakpoint, a clickable prototype, an accessibility checklist and a written handoff for developers. You own all of it: files, accounts and IP transfer to you.
We test clickable prototypes with people who match your users and watch where they hesitate, misread a label or give up. A problem found in a prototype costs a conversation to fix. The same problem found after launch costs a release. Findings and decisions are written down.
Yes. If you have a brand system we apply it and extend it where the product needs rules the guidelines never covered, such as data tables, empty states or error messaging. If you do not have one, we document the type scale, colour roles and spacing rules the product needs.
It means contrast, focus visibility, target size, consistent help, clear labels and keyboard operability are settled while the screens are being designed. We review the designs against the criteria before handoff, so the build team is not left to guess or to retrofit it later.
The studio is in Vancouver and clients elsewhere are served remotely, with video calls scheduled in your time zone and on-site visits when a workshop or a research session calls for it. We reply to every enquiry within one business day. Request a quote and we will take it from there.
Let’s connect
Tell us what you’re building. We’ll reply within one business day with next steps and a tailored quote — no obligation.