Mobile apps
iOS and Android. Short moments between other things, a thumb instead of a mouse, and notifications that help instead of annoying.
Case study:WellysaBack to the home page
Digital products
I design mobile apps, web apps and dashboards that people use without a manual. I take a product from the first conversation about the idea, through research and a prototype, to screens ready to build.
- UX/UI
- Wireframing
- Prototyping
- Interaction Design
- Usability testing
Prototype
O
Good morning, Ola
You have one recommendation this month
Recommended
Check-up visit
Your last one was 11 months ago
Upcoming
- Online consultationFri, 16 October, 18:00
- Blood testMon, 2 November, 7:30
HomeVisitsResultsProfile
Pick a time
Check-up visit, 30 minProsta 12 Clinic · 0.7 mi
Mon5Tue6Wed7Thu8Fri9
More times
We’ll remind you the day before
Done, see you then!
Tuesday, 6 October, 10:00
Check-up visit, 30 minProsta 12 ClinicWe’ll remind you the day before
Add to calendarWhat I design
A digital product is an app, a dashboard or an online service your customers use every day. Every screen either brings them closer to their goal or makes them guess. My job is to remove the guessing.
Web apps and SaaS
Tools people work in, right in the browser: accounts, permissions, settings and dozens of screens that have to work as one.
Dashboards and admin panels
A lot of data in a small space. Hierarchy, filters and tables where what needs attention is visible at a glance.
AI products
Chats, assistants and knowledge search. I design for trust: where an answer comes from, what the AI does not know and how to correct it.
Case study:SesameUsability
Every extra step is a customer who gives up
One goal: book a visit. First, the path I often find in products before they are designed. Flip the switch and see what is left once every screen has to justify why it exists.
- Screens
- 1010
- Taps
- 1616
- Fields to type
- 77
- 1A welcome screen every time the app opens.
- 2Email and password on every visit.
- 3Three screens of searching: menu, list of services, map of locations.
- 4A form asking for data the app already has.
- 5Day and time picked on two separate screens.
- 6A summary that repeats what you have just chosen.
In Wellysa it takes two taps to get from a recommendation to a booked appointment.See how I did it
Process
From an idea to a product that works
Seven steps in which a single screen goes from a note taken in our first conversation to a spec for developers. After each one you see the progress and make the calls before anything goes into code.
- Stage 1 · Discovery
Conversation and goals
I start with your business, not with screens. We agree who the product is for, what should change once it ships and how we will know it worked.
What we do
- A workshop with you and your team
- Business goals and constraints
- A measure of success
What you get
- Product brief
- Scope of the first version
Your call: You sign off the goals and scope.
- Stage 1 · Discovery
Research
I talk to the people who will use the product and look at how they manage without it today. This is often where it turns out the real problem is somewhere other than we assumed.
What we do
- User interviews
- Competitor review
- Analytics, if the product is already live
What you get
- Personas
- Experience map
- List of findings
Your call: You help me reach your customers.
- Stage 2 · Design
Architecture and flows
I lay the product out like a map: which screens there are, how they connect and which way a user gets to their goal. It is the cheapest moment for changes, because we move arrows, not code.
What we do
- Screen map
- User paths
- Edge cases
What you get
- Information architecture
- User flows
Your call: You approve the paths and the order of work.
- Stage 2 · Design
Wireframes
I sketch the key screens in greys, with no colour and no photos. We talk about what is on the screen and in what order, not about the shade of a button.
What we do
- Sketches of key screens
- Content hierarchy
- First drafts of the copy
What you get
- Wireframes of key screens
Your call: You choose the direction.
- Stage 2 · Design
Interface design
Wireframes get your brand: typography, colour, icons and motion. I design every state of every screen and build them from components your team will use for the next features.
What we do
- Visual direction
- Every screen and its states
- Components and tokens
Your call: You approve the look.
- Stage 3 · Prototype and testing
Prototype and testing
I link the screens into a clickable prototype that behaves like the app. I hand it to a few people from your audience and watch where they get stuck. Fixes cost hours here, not weeks of development.
What we do
- Clickable prototype
- Testing with users
- Fixes after testing
What you get
- A prototype to show investors and the team
- Test report
Your call: You decide which fixes go in.
- Stage 4 · Launch and support
Handoff and launch
Developers get a design with sizes, states and rules of behaviour. I stay on the project: I answer questions and review the built screens before they reach users.
What we do
- Developer spec
- Review of the built screens
- Support after launch
What you get
- Files ready to build
- List of fixes from the review
Your call: You ship the product.
Details
Usability is the sum of small decisions
Nobody praises an app for a good error message, but everyone remembers the one that lost what they had typed. A product holds hundreds of these decisions. Flip the switch to see six of them.
- Error 422: invalid input data.EmailTypo? Did you mean gmail.com
Error message
It says what went wrong and how to fix it, right next to the field it is about.
- Check-up visitTue, 6 October, 10:00Online consultationFri, 16 October, 18:00
Are you sure?
This action cannot be undone.
NoYesVisit deletedUndo instead of asking
The action happens straight away and can be undone for a few seconds. No “Are you sure?” pop-ups.
- Check-up visit20 × 20 ptClose
Touch target
A button is at least 44 points, even when its icon is smaller. A thumb is not a cursor.
Check-up visit
Tuesday, 10:00
#B4B4AE2.1 : 1 · AALegibility
Text contrast that meets WCAG. The app can be read in sunlight and without glasses.
Feedback
A tap shows straight away that something is happening, and a moment later that it worked.
An error occurred
The operation failed (code 0x80070005).
OKInterface copy
Buttons say what they will do, and messages sound like a person, not like a server.
Screen states
One screen, five versions
A mock-up usually shows a screen on its best day: the data is there, the internet works, the user knows what they are looking for. I design the other versions too, because they are where people most often give up.
Screen states1/5
1First visit
An empty list is an invitation to take the first step, not a dead end.
Work
Two products designed from scratch
A mobile health app and an AI tool for companies. Different industries, the same process.
Mobile app, health
Wellysa
A personal health assistant that turns test results into one concrete next step and guides people from a questionnaire to a booked appointment.
What I designed- Information architecture and flows
- Step-by-step health questionnaire
- Booking a test at a collection point
- Wellysa Club, the social layer
- Profile sources
- 3
- Recommendation to booking
- 2 taps
- Scope
- App 0→1
Web app, AI for companies
Sesame
A secure workspace with an AI chat that gives a company access to all of its internal knowledge without losing control over its data.
What I designed- New information architecture
- Chat and file management flows
- Permissions and workspaces
- Three interface concepts
- Flow maps
- 120
- UI concepts
- 3
- Scope
- 0→1
PlaceholderSpace for another productA third case study: a shot of the screens, the type of product and two or three sentences about the problem the design solved.
PlaceholderSpace for a client quoteA short quote from the Wellysa or contexxt.ai team about what the design changed. Name, role and company.
Working together
What you can come to me with
I have an idea for an app
A new product from scratch
From a workshop and research to a tested prototype and screens ready to build. I help you decide what has to be in the first version and what can wait.
First stepA workshop on goals and scope
We have a product, but people get lost in it
UX audit and redesign
I look at the product through your users’ eyes, talk to your customers and dig into the data. You get a list of problems ranked by business impact and a design for the fixes.
First stepA review of the product and data
We have a team, but no designer
A designer on your team
I join your product team: I work in your sprints, with your product manager and developers, and I own the user experience.
First stepA conversation about your roadmap
You work with me directly
From the first conversation to reviewing the build. No middlemen, and no handing the project on to other people.
FAQ
Before we start, you will probably ask this
With a conversation. A few sentences about who the product is for and what it should change are enough. We put together the brief, the scope of the first version and the plan of work in the first stage.
It depends on the scope. A single flow in an app usually takes two to four weeks, while a product built from scratch is measured in months. After our first conversation I give you a specific date and stick to it.
I price every project individually, based on its scope and complexity. After a short conversation I will prepare an offer tailored to your needs.
For digital products I focus on UX/UI and hand the build over to a development team: I work closely with them and can recommend people I trust. After handoff I stay available and review the built screens.
Not always. For a new product, or when the risk of getting it wrong is high, a few interviews and a prototype test pay for themselves quickly. For smaller changes an expert review and the data you already have are enough.
The design of every screen and its states in Figma, a component library, a clickable prototype and a spec for developers. We agree the scope at the start, so you know what you will get before we begin.
Every stage ends with a meeting where I show the progress and collect your comments. We only move on once you approve the direction, so nothing surprises you at the end.