UX design for apps people actually keep using.
Our UX practice is built on user research and behavioural psychology, not assumption. Every flow, gesture, and screen decision is grounded in evidence about how real people use apps. This is where commercial success is either enabled or undermined.
What it is
UX is the architecture of the experience. UI is how it looks.
Most people use the terms UX and UI as if they describe the same thing. They do not. UX design is the logic of the product, the flows users move through, the decisions about what happens when, and the structure underneath every screen. UI design is the visual layer that sits on top of that structure. Both matter. We design both. This page is about the UX work specifically.
UX design covers user flows and information architecture, interaction design and gesture logic, wireframing and prototyping, usability and accessibility, and the relationship between how a product works and whether people come back to it. None of these are decorative. They are the load-bearing decisions in a product, and they are made before a single pixel of visual design is applied.
An app can look beautiful and still fail. A user opens it, gets lost in the first thirty seconds, cannot work out how to do the thing they came for, and deletes it. That is a UX failure dressed up in a UI success. The opposite is rarely true. A product with a clear, well-considered UX can survive an average visual design. A product with broken UX cannot be saved by a beautiful one.
The work begins with understanding people. How they think, what they expect, what they find confusing, and what they do when they hit friction. That understanding becomes the architecture, and the architecture becomes the product.
Why it matters
UX design is the highest-return decision in an app build.
Fixing UX problems after launch costs many times what it costs to design them properly upfront. The cost is not only the rework. It is the engineering hours spent rebuilding flows that were never right, the users lost during the months it takes to fix them, and the brand damage from a product that frustrated people in its first weeks. UX done well at the start is the cheapest UX you will ever buy.
UX problems almost always show up as retention problems. Founders look at a drop-off after day one and assume the issue is the marketing, the audience, or the price. Usually it is the experience. People open an app, cannot work out what it wants from them, feel slightly stupid, close it, and never return. They will not tell you why. They will just stop using the product.
Users form an opinion in the first three seconds of opening an app. Not the first session. The first three seconds. By the time they have scrolled once, they have already decided whether this product feels trustworthy, whether it understands them, and whether it is worth the effort of learning. That judgement is almost entirely a UX judgement, made before they have processed any of the visual design consciously.
The word “intuitive” gets used a lot. It is worth being precise about it. Intuitive means the next action is obvious because the design has anticipated where the user’s attention will land and what they will try to do. Intuitive is engineered. It is the result of research, testing, and careful choices about hierarchy and sequencing.
Where UX problems show up
| Metric | Status |
|---|---|
| First-session drop-off | High |
| Day 7 retention | Low |
| Core task completion | Patchy |
| Support enquiries on basic flows | Rising |
When founders describe a “retention problem”, these are usually the four patterns underneath it. All four are UX problems before they are anything else.
Our process
How we approach app UX design.
Five stages, each with a specific output that feeds the next. No stage is skipped to save time. Skipping any one of them is the most common reason an app launches with the wrong product underneath the right visuals.
Stage 01
Discovery and user research
Before a single screen is drawn, we invest in understanding the people who will use the product. Stakeholder workshops, user interviews, behavioural analysis, and competitor review. This is what makes everything that follows accurate rather than assumed.
Stage 02
Information architecture
Mapping the product’s structure before designing its surface. What screens exist, how they connect, what decisions users make at each point, and where the natural pause points sit.
Stage 03
User flows and interaction design
Designing the logic of how users move through the product. Every interaction has intent behind it. We design for the real user, who is distracted, impatient, occasionally confused, often on a poor connection, and rarely paying full attention.
Stage 04
Wireframing and prototyping
Low and mid-fidelity prototypes that test structure and flow before any visual design is applied. Problems caught at this stage cost a fraction of what they cost to fix once a feature is live.
Stage 05
Handoff to UI design
UX outputs feed directly into our UI design process. Nothing is thrown over a wall. The team that designed the UX works with the team designing the UI, which means the structural intent survives the visual translation.
What you get
The deliverables.
Each item below is a working document, not a reassurance. Everything goes into the build brief that gets handed to developers, and everything ties back to the research that came out of the first stage.
| Deliverable | What it is and what it does |
|---|---|
| User research report and personas | The research record from interviews, behavioural analysis, and stakeholder sessions, distilled into the specific user types this product is being built for. |
| Information architecture map | The structural map of the product. Every screen, every connection, every branch. |
| User flow diagrams | Step-by-step flows for every core task, including the edge cases and error states. |
| Annotated wireframes | Mid-fidelity wireframes of every screen, annotated with the logic and intent behind each decision. |
| Interactive prototype | A clickable prototype that lets you walk through the flows before they are built. Used for stakeholder review and user testing. |
| UX specification document | The complete handoff document for development. Behaviour, states, transitions, edge cases, and the rationale for every non-obvious decision. |
Common mistakes
What goes wrong when UX is treated as a step rather than a foundation.
We see these patterns repeatedly. None of them are unusual, and none of them are a sign of an inexperienced team. They are a sign of a process that did not give UX the room it needed.
Mistake 01
Designing for the happy path only. The product works beautifully when the user does exactly what was expected. Real users almost never take the happy path the first time.
Mistake 02
Skipping research to save time and budget. Research feels like a delay. It is the opposite. Every week of research saves months of rebuild.
Mistake 03
Treating UX as a single handoff. UX is not a phase that ends. It is an iterative practice that continues through build, launch, and beyond.
Mistake 04
Conflating UX with UI. Prioritising how it looks over how it works. The user flows never get reviewed in detail.
Mistake 05
Not designing for the distracted user. First-time users are not focused. They are on a train, between meetings, or half-watching something else.
Mistake 06
Assuming intuitive happens by accident. “Intuitive” is the most common word in product briefs and the most rarely engineered.
Frequently asked
How long does UX design take?
The honest answer is that it depends on scope, the depth of research required, and how clear the product proposition already is at the start.
Do I need UX design if I already have a developer?
Yes. Developers build what they are briefed to build. They are not paid to question whether the flow makes sense.
What is the difference between UX and UI design?
UX is the architecture of the experience. The flows, the structure, the logic of how users move through the product, and the behaviour of every interaction. UI is the visual layer that sits on top.
Can I see examples of your UX work?
Yes. Our Harley engagement is a good place to start, because it shows how research, information architecture, and flow design fed directly into the final product.
Start here
Three ways to begin.
- Path 01 · Send details: Tell us about the product, the audience, and where you are in the process.
- Path 02 · Talk it through: Thirty minutes to walk through what you are building and what you need.
- Path 03 · Understand the cost: See pricing, the numbers, the engagement options, and what is included in each.