Product design review

Host onboarding for a home-swapping app

Review of the host onboarding flow used when a new member lists their home, sets swap rules, and publishes availability. The goal is to reduce drop before photo upload and improve host confidence.

Flow under review: 4 screens Reviewer: Product design Last updated: May 2026 Status: Needs iteration
Strong panels1
Panels needing rework3
Decision items5
Open questions4

Annotated wireframes

Panel review

Switch panels to focus on one screen at a time. The default view shows the first screen because it drives most downstream completion risk.

1. Intro and host motivation

Progress 1 of 4
Become a host
Explain how home swapping works and why listing now matters.
Trust signals
ID verification later
No public address until approved
Observation The hero and the first two actions compete for attention. Hosts do not know whether to start listing or keep reading.
Recommendation Replace the second call-to-action with a compact reassurance strip and keep one clear primary button.

Decision log

What to change now

Item Decision Why
Intro CTA stack Reduce to one primary action Current screen introduces choice anxiety before commitment.
Photo upload timing Move after home basics Photos feel high effort before hosts feel progress.
Rule chips Add helper text and grouping Hosts need to understand how these settings affect match quality.
Progress indicator Show task names, not just numbers Numbers alone do not communicate remaining effort.

Alternatives considered

What we are not doing

Alternative A: single long scroll form

Rejected. It exposes every decision at once and makes host onboarding feel heavier, especially on mobile.

Alternative B: ask for photos first to increase listing quality

Rejected for first-time hosts. This likely improves final listing quality but hurts top-of-funnel completion.

Alternative C: hide rules until after publish

Partially rejected. Some rules must be known before publish to prevent poor swap matches and low trust.

Unresolved question

Verification timing

Should identity verification happen before publish, or only before the first accepted swap request?

Unresolved question

Calendar defaults

Do hosts understand blocked dates better if we pre-fill the next 60 days as unavailable instead of blank?

Unresolved question

Trust messaging

Would a stronger privacy explainer on screen one improve progression to photo upload, or is it secondary to action clarity?

Compact recommendation

Next iteration

Keep the four-step architecture. Rework screen one to reduce choice overload, delay photos until after home basics, and borrow the publish screen's reassurance language earlier in the flow. That combination is the highest-confidence path to better completion without lowering host quality.

Hosted onPagrยทShare your HTML files