UX/UI Design · Bilwebben · UX/UI design and design system
Redesigning the journey from car search to dealer contact
Bilwebben brings together new and used vehicles from dealers across Sweden. But the existing website made search and filtering difficult to find and use, and the experience needed rethinking to better support buyers from their first search through to contacting a dealer.
As the sole UX/UI designer, I worked closely with the founder and developers to redesign the buying journey, from search and filtering to vehicle information and dealer contact. I also designed new service flows and created a shared design system to bring the experience together across desktop and mobile.
- My role
- UX/UI designer
- Team
- Founder and developers
- Platform
- Web, desktop and mobile
- Status
- Design delivered, not yet live when I left
- Period
- 3 months, spread over 2025–2026
The short version
The challenge
Bilwebben had a large selection of vehicles, but search was easy to miss and the filters offered limited ways to narrow down listings. The listing page and several longer service flows also needed a clearer structure.
The challenge was to create a more coherent experience from the first search to the next step in buying a car, while making room for new services.
What I did
I reviewed the website’s UX and ran a few quick usability tests focused on search and filtering.
I then redesigned the homepage, search, filters and listing page. I also designed flows for services including car loan applications and new-car configuration, as well as the logged-in experience.
As the sole UX/UI designer, I was responsible for information architecture, interaction design, UI and the design system, working closely with the founder and developers.
What I delivered
Completed Figma designs for desktop and mobile, covering the marketplace’s main journeys, new services and partner integrations.
I also created a shared design system with reusable components, using the same naming conventions in Figma and code.
The designs were delivered for development, but the new website had not launched when I left the project.
My responsibilities as UX/UI designer
UX and information architecture
I reviewed the buyer journey and reworked the structure of the homepage, search, filters and listing page.
UI design for desktop and mobile
I created detailed Figma designs for the marketplace’s main journeys and new services.
Interaction design for longer flows
I designed step-by-step forms, summaries and navigation to help users keep track of their progress.
Design system
I owned the shared colours, typography, design variables and reusable components, with accessibility in mind.
Integrated partner services
I designed a Bilwebben loan application intended to use the partner’s API instead of an embedded form.
Close collaboration with developers
We used consistent component names in Figma and code to make collaboration between design and development easier.
Understanding buyers
Before redesigning the website, I wanted to understand how visitors searched through the listings and where they ran into problems.
User testing wasn’t a priority in the project, but I wanted a stronger basis for my design decisions. So I ran a few quick usability tests focused on search and filtering. I also carried out my own UX review of the website, from the homepage to the longer service flows.
Together, they revealed four areas that needed attention.
What the usability tests revealed
Search was difficult to discover
None of the participants found the search function. It was tucked away in the navigation, despite being one of the site’s most important features.
What the usability tests revealed
Filters were hard to find and too limited
Participants struggled to find the filters. Once they did, there weren’t enough options to narrow down a large number of listings effectively.
What I found in my UX review
Longer flows lacked a clear overview
When configuring a new car or applying for a loan, visitors couldn’t easily see how many steps were involved, where they were or what remained.
What I found in my UX review
Partner services disrupted the experience
Several services appeared in iframes with a different look and behaviour from the rest of Bilwebben. This made the experience feel disconnected, particularly in longer flows.
That became an important starting point for designing interfaces that could use the partners’ APIs instead.
Using the buyer journey to guide the design
I structured the work around five stages: arriving on the site, searching, narrowing down the results, looking more closely at a vehicle and taking the next step.
For each stage, I considered what buyers needed to do, which problems we had identified and how the design could support them.
This gave the work two clear priorities: making relevant vehicles easier to find and giving buyers the information they need before contacting a dealer.
The next two sections show how I approached those challenges.
From search to shortlist
The usability tests showed that search was difficult to discover and that the filters weren’t sufficient for narrowing down a large number of listings.
I redesigned the homepage, search and filtering around a simple goal: make it easy to get started, then progressively narrow the results to relevant vehicles.
Giving search a prominent place
The new homepage starts with what most visitors come to do: find a vehicle.

- Start with vehicle searchA prominent search field lets visitors enter a make, model or specific features, with suggestions appearing as they type.
- Keep search in the navigationA global search remains available across the site. It covers vehicle listings as well as news and guides.
- Choose new or used from the startVisitors can select all, new or used vehicles before entering their search.
- Make room for explorationThe homepage also presents vehicle categories, from cars and vans to motorhomes, caravans and motorcycles, with listing counts for each.
Before and after – a clearer starting point
On the old homepage, search appeared as a small link in the navigation. The main area was taken up by a banner, a button and several information boxes.
In my redesign, vehicle search became the main feature. I placed it prominently on the page, with new and used options and suggestions for makes and models as visitors type.

- Search is a small link in the menu.
- The banner has one button and no search field.
- Five boxes of selling points, and no way to narrow down from here.

- A search for vehicles in the middle of the page.
- All, used or new, right above it.
- Makes and models suggested as you type.
- The global search stays in the menu.
One search wasn’t enough
I initially explored using the global search in the navigation for everything.
What worked and what didn’t
It worked for searching across different kinds of content, but didn’t give vehicle search enough prominence on the homepage.
Two entry points
I therefore designed two entry points with different purposes: a dedicated vehicle search on the homepage and a global search in the navigation.
From results to a manageable shortlist
Once visitors have started searching, they need a straightforward way to narrow down the results. Click an image to enlarge it.
From listing to dealer contact
Once buyers find an interesting vehicle, the listing needs to answer a few important questions: What is the car like? What do we know about its condition and history? Who is selling it? And how can I take the next step?
I redesigned the listing page to make information easier to scan and bring the ways of contacting the dealer together.
Vehicle information that’s easier to explore
- Give photographs room to leadA large main image is supported by thumbnails and a counter, such as 13 of 35. Visitors can browse the photographs and see how many are available.
- Make vehicle details easier to findI organised the information into seven expandable sections. Buyers can check mileage, equipment and other details without scrolling through the entire listing.
- Bring vehicle history forwardA dedicated card shows how many events are recorded and what the report covers, including damage, ownership, inspections and mileage. Buyers can open the report directly from the listing, free of charge.
Keep the dealer visible
- Bring essential information togetherThe dealer’s name and location, price and date of the latest listing update sit in a card that stays visible while scrolling.
- Show who buyers are contactingThe contact view includes the dealer’s address, a map, directions and a link to the rest of their stock. Buyers can find out more about the dealer or explore other available vehicles.
Give buyers clear ways forward
- One primary actionI gave contacting the dealer a prominent green button, with the option to call directly for those who prefer it.
- Different ways to make contactNot everyone wants to get in touch in the same way. I designed five options, including booking a test drive, requesting a call, asking about a trade-in or sending a message.
The form adapts to the selected option and asks only for relevant information. - Place financing beside the priceI positioned the estimated monthly cost and financing option alongside the vehicle price, making them available when buyers consider their options.
Partner services that fit the listing
- One pattern for different offersVehicle history, insurance and financing use the same underlying card pattern: a short description, relevant benefits and one clear action.
Each partner retains its own colours, making it clear who provides the service. - Connect the offer to the vehicleRather than displaying a generic loan promotion, the financing offer refers to the vehicle being viewed. This places it in the context of the buyer’s current decision.
The whole journey on mobile
I designed the same journey for mobile, adapting how information and actions appear on a smaller screen. Click a screen to enlarge it.
Applying for a car loan
Bilwebben offers car loans through a partner. The previous solution displayed the partner’s ready-made form in an iframe.
I was given the opportunity to design a Bilwebben application flow instead, which the developers could build using the partner’s API.
The aim was to give buyers a clearer overview and make the application follow the same design principles as the rest of the website.

- Three numbered dots, with no names.
- Loan details and personal details in one long column.
- The partner’s own fields, help icons and blue button.

- Named steps, and only this one open.
- The monthly cost, large and in plain words.
- The site’s own green button.
- The steps still to come.
- Show the full journey from the startThe steps Desired loan amount, About you and Send make the scope of the application visible. Only the current step is open, but the upcoming steps remain in view.
- Help buyers keep trackOnce a step is complete, it collapses into a short summary, such as SEK 343,000, 8 years. Buyers can return and edit their answers without starting again.
- Keep the interface consistent with BilwebbenFields, typography and buttons follow the design system. The application remains visually part of the website, even though the loan is provided by an external partner.
- Explain why information is neededFor the co-applicant question, I added a short explanation and two clear choices instead of relying on a dropdown with a help icon.

- Step one, folded into one line with a pencil to edit it.
- The co-applicant question, with a reason and two buttons.

- Both earlier steps are summaries now.
- One last question, then two consents and the button.
New services, same design foundation
As the project progressed, more services and pages were added. I designed them using the same components and principles as the marketplace, allowing new functionality to become part of a coherent experience.
- New-car configuratorI designed a step-by-step flow where buyers choose vehicle features, equipment, engine and options. A price summary updates as choices are made and stays visible throughout the process. Once the configuration is complete, buyers can submit an expression of interest.
- Dealer pageI brought together information about the dealer, contact details, a map and their available vehicles. The listings use the same vehicle cards and filters as the search results, so the interaction patterns remain familiar.
- Bilweb NewsFor articles, guides and reviews, I reused the marketplace’s search-and-filter approach while adapting the available filters to the content. This made it possible to build on existing components even when the service served a different purpose.
A shared design system
I owned Bilwebben’s design system. It gave the website a consistent visual foundation and made it possible to reuse components as new pages and services were added.
It also became a shared reference in my collaboration with the developers.
- Blue#1190C6Brand, links
- Green#108C69Main actions
- Dark#141B34Dark surfaces
- Grey 900#212121Text
- Blue 50#E9F6FBSoft surface
- Green 50#EAF7F4Soft surface
- Grey 100#F5F5F5Background
Colours are managed as shared variables in Figma.
- Heading 232 · Semi Bold
- Nytt och begagnat från Sveriges bilhandlare
- Heading 324 · Bold
- Sök efter fordonstyp
- Heading 420 · Semi Bold
- Dags att byta bil?
- Subtitle16 · Semi Bold
- Riddermark Bil – Megastore
- Body16 · Regular
- Hos oss kan du köpa noggrant kontrollerade fordon från pålitliga bilhandlare.
- Body small14 · Regular
- Räkna ut priset för din Volvo XC60.
- Caption12 · Regular
- 60 800 annonser
- Button15 · Medium
- Visa alla bilannonser
- Components across the buyer journeyI created reusable components for navigation, search, filters, vehicle cards, partner offers, accordions, buttons and step-by-step forms.
The components were designed for desktop and mobile, with interaction states and accessibility considered as part of the design. - The same language in Figma and codeWe used consistent component names in the design files and code, including Button, Accordion and CardActions.
This made it easier to discuss changes, keep design and development aligned, and reuse solutions across the product.
What I took with me
I’d start with the design system again. It helped me keep the experience consistent from search and listings to the loan application and new services. It also made collaboration with the developers easier.
One thing I’d change is agreeing on what to measure earlier in the project. I encouraged the team to define measurable outcomes, but it didn’t get enough attention. Since I left before the new website launched, I don’t have results from real usage to report.
I’d also work differently with the tools today.
I’d still begin in Figma to explore the direction and establish the design system. But I’d move into Claude earlier and continue designing in working code.
That would let me try responsive layouts and interactions directly, give others something they can test on their own phones, and provide developers with a handover closer to what they’ll actually build.
For me, it isn’t about doing less design. It’s about testing my decisions earlier, in a more realistic setting.
“Mikaela made us explore different possibilities quickly, going from an idea to something we can discuss or ship.”