Creating a Rental Listing in 60 Seconds

ImmoScout24 enables tenants to create rental listings when searching for a tenants.

The existing native app flow was based on a multi-step wizard that required users to navigate through several screens. While functionally complete, the experience felt lengthy and cognitively demanding especially for users who simply wanted to publish a listing quickly.

The business goal was ambitious: Enable users to create and publish a listing within 60 seconds.

Create a listing · Android

Challenge

Reduce time-to-publish significantly
Lower bounce and dropout rates
Simplify cognitive load
Ensure scalability within the native app architecture

My Role & Responsibility

UX concept & structural redesign
Benchmark & hypothesis validation
A/B test definition & evaluation
Prototype development & user testing
Close collaboration with Product & Engineering

The 60-second target required a radical simplification of the process not just incremental improvements.

Create a listing

Approach

1. Benchmark & Existing Assets

We already had a promising One-Pager flow on web, which felt faster and more transparent than the traditional multi-step approach.

After conducting a benchmark analysis, we decided to validate the assumption: Would a One-Pager outperform the classic multi-step wizard inside the app?

2. A/B Testing the Web Flow in App Context

We integrated the web-based One-Pager into the app and ran an A/B test against the native multi-step flow.

After conducting a benchmark analysis, we decided to validate the assumption: Would a One-Pager outperform the classic multi-step wizard inside the app?

Results showed significant improvements in:

Bounce rate
Dropout rate
Completion speed

This validated our core hypothesis: Reducing perceived process length increases completion.

3. Native Optimization

Despite improvements, the web flow still had structural weaknesses when translated to mobile.

For the native version we:

Restructured the form to visually resemble a real listing
Grouped fields based on mental models rather than backend logic
Reduced visual fragmentation
Prioritized high-impact fields first
Prioritized high-impact fields first

4. User Testing & Iteration

We created an interactive prototype and conducted user tests.

Key learnings:

Users preferred contextual grouping over step logic
Grouped fields based on mental models rather than backend logic
Perceived speed mattered more than actual milliseconds

5. Final A/B Test & Rollout

We created an interactive prototype and conducted user tests.

Key learnings:

Users preferred contextual grouping over step logic
Grouped fields based on mental models rather than backend logic
Perceived speed mattered more than actual milliseconds

Impact

arrow_downward Dropout rate reduced significantly
arrow_downward Bounce rate improved measurably
arrow_downward Time-to-publish shortened substantially
arrow_downward Bounce rate improved measurably
arrow_outward Higher completion confidence reported by users

Handover for development

Key Learnings

Multi-step flows can create psychological friction
Perceived length is more critical than actual length
One-page flows require strong structural hierarchy
Speed targets create clarity in decision-making

While not a mass-adoption feature, the initiative successfully served as an experimentation and learning platform.