← All design studies

Screen study · Reviewed September 23, 2026

Depop signup: email handoff, validation and first browse

Six screens show the handoffs and recovery details between signing up and browsing.

How do you keep people oriented when signup leaves the app?

The exported screens include an explicit inbox instruction, contextual field help and a clear browsing destination. The lesson is to make the next action and the recovery path visible at each handoff.

Evidence and limits

Selected July 2026 exported iOS screens, presented in archive order. No Depop recording is attached, so transition timing, intermediate actions and alternative paths have not been verified.

Read the decisions

Depop: The signup or login screen asks for an email address and shows an inactive Continue action.

01 / Depop · Jul 2026 · Still image

Start with one field

What is visible

The signup or login screen asks for an email address and shows an inactive Continue action.

Design interpretation

A shared entry point avoids requiring someone to decide whether they already have an account. Explain what the next action will do.

Depop: The next screen asks the person to check their inbox and offers an Open email app action. The explanatory text distinguishes an existing account from a new one.

02 / Depop · Jul 2026 · Still image

Explain the email handoff

What is visible

The next screen asks the person to check their inbox and offers an Open email app action. The explanatory text distinguishes an existing account from a new one.

Design interpretation

Give the person a next action and a recovery route when a flow leaves the app. The export does not show link delivery time or reliability.

Depop: The birth-date screen says the date is needed for safety and will not appear on the profile. A help link offers further explanation.

03 / Depop · Jul 2026 · Still image

Explain a personal-data request

What is visible

The birth-date screen says the date is needed for safety and will not appear on the profile. A help link offers further explanation.

Design interpretation

Place the reason near a sensitive field and describe visibility. Treat the explanation as a product claim, not independent verification of its data practices.

Depop: A short username triggers an inline message saying it must be at least three characters. The field is outlined in red.

04 / Depop · Jul 2026 · Still image

Put validation next to the field

What is visible

A short username triggers an inline message saying it must be at least three characters. The field is outlined in red.

Design interpretation

Describe the correction in text, not only color. In a web implementation, associate the message with the input and preserve what was typed.

Depop: Stay in the loop lists purchase tracking, offers and messages as benefits. No thanks and OK cool are both visible.

05 / Depop · Jul 2026 · Still image

Offer a notification choice

What is visible

Stay in the loop lists purchase tracking, offers and messages as benefits. No thanks and OK cool are both visible.

Design interpretation

Make declining straightforward. This screen does not show the native permission dialog or prove what happens after either action.

Depop: The home screen shows product cards and invites the person to tap items for better picks.

06 / Depop · Jul 2026 · Still image

Reach a populated destination

What is visible

The home screen shows product cards and invites the person to tap items for better picks.

Design interpretation

Let preference learning continue through meaningful use instead of putting every question into setup. We cannot infer the recommendation algorithm from this screen.

What to question

  • An email link removes password entry from this path but adds a context switch. Plan for delayed messages and a return to the app.
  • Date-of-birth collection adds effort and needs a clear purpose. Request only information the product actually needs.
  • Inline validation can help recovery, but a screenshot cannot establish screen-reader announcements or keyboard behavior.

Try an original implementation

Explore a three-step web onboarding pattern: choose a goal, set a pace, and optionally request a reminder. Go back to revise answers without losing them.

This React example uses native form controls, keyboard navigation and focus management. It is a separate prototype with original copy and styling, not a reproduction of the source apps.

Download React source

Requires React and Tailwind CSS. Web only; not React Native. MIT license.

Import the named OnboardingExample component into a page. Replace the final preview with your application logic; this example makes no network requests.

Practice studio · Original web demo

Step 1 of 3

What would you like to practice?

Choose one goal. You can change it before finishing.
Explore five more original interactive examples →

Before you ship

  • Tell people which inbox to check without unnecessarily exposing an address.
  • Provide a way to correct the email and request another message.
  • Explain each personal-data field near the input.
  • Keep optional communication choices separate from account creation.

Validate these recommendations with your own users. No conversion uplift is claimed.

Continue the research