Make effort visible
A transparent one-page structure reduced the feeling of being trapped inside a long wizard.
Back to work
Case Study / Mobile Listing Flow
Creating a rental listing in 60 seconds.
I redesigned a lengthy native listing wizard into a faster, more transparent creation experience by making the flow feel like building a real listing, not filling a backend form.
Context
Private landlords creating rental listings directly in the ImmoScout24 app.
Role
UX concept, structural redesign, prototyping, user testing and A/B-test support.
Decision
Replace step-by-step progression with a clearer one-page mental model.
Impact
Successful product direction with reduced friction and higher completion confidence.
The Challenge
Goal: speed. UX problem: perceived effort.
ImmoScout24 wanted private landlords to create and publish a rental listing directly from the app within 60 seconds. The existing native flow was functionally complete, but it asked users to move through several screens and made the process feel longer than it needed to be.
The design challenge was not cosmetic. The flow needed a structural rethink: fewer transitions, clearer grouping, visible progress and a stronger sense that users were creating a real listing rather than completing an abstract form.
Design Judgment
Redesign the mental model.
Group by user logic
Fields were organized around landlord mental models instead of backend or technical categories.
Protect feasibility
The final direction balanced speed, usability and what could be delivered inside the native app architecture.
Before / After
From wizard to one-page flow.
- Several screens with repeated transitions
- Progress felt fragmented and hard to estimate
- Fields reflected system structure more than user intent
- The flow felt longer than the actual input effort
- One-page direction with more visible progress
- Sections grouped around real listing context
- Fewer navigation moments between inputs
- Faster confidence before publishing
Approach
Validate before building native.
We already had a promising one-page flow on web. I used that pattern as a hypothesis: if users could see the shape of the entire task, the flow would feel shorter and more manageable than the classic multi-step wizard.
The web-based one-pager was brought into the app context and tested against the native flow. The direction showed clear improvements in bounce, dropout and completion speed, strong enough to justify native optimization and rollout.
Research Signals
Perceived length mattered.
Users understood the task faster when they could see the structure of the listing creation process.
Grouping inputs by real-world listing context made the flow easier to scan and complete.
The experience felt faster when users had fewer transitions and less uncertainty about what came next.
Impact
Validated by rollout and testing
User impact
Users had a clearer sense of progress, lower perceived effort and higher confidence before publishing.
Business impact
The project was considered a strong success and supported a lower-friction path through a business-critical listing flow.
Product impact
Testing and A/B signals showed improvements in bounce, dropout and completion speed, supporting native optimization and rollout.
Learning
Speed goals should change structure.
The main lesson was that time-to-publish is shaped by more than the number of fields. It is shaped by how effort is framed, how progress is made visible and whether the interface follows the user's mental model.
For this project, the 60-second target became a design constraint that helped the team make sharper decisions about hierarchy, grouping and interaction cost.
Next
Explore another product story.
Contact
LinkedIn
