Five Products on Page Flows That Every Product Designer Should Study Before Starting Their Next Project
(STL.News) Most designers collect inspiration from design portfolios, Twitter threads, and Dribbble shots. Those have their place, but they rarely show how a product works end-to-end, how it handles friction, how it guides users through awkward moments, or how it recovers from errors. The products section on Page Flows solves that gap by showing complete, recorded flows from real apps, annotated and searchable by product name. If a designer has twenty minutes before a new project kicks off, spending them at https://pageflows.com/all-products/ is a better use of time than most kick-off rituals.
Five products on the platform stand out above the rest, not because they are the most famous, but because each one teaches a specific lesson that transfers across almost any project type.
1. Duolingo
The Case for “Play First, Profile Second”
Duolingo’s onboarding is one of the most studied flows in the industry for a reason. The app puts users through a short lesson before asking them to create an account. By the time the signup screen appears, users have already earned XP, completed a task, and seen how the product works. That sequence changes the psychological dynamic entirely. The account creation screen arrives at a moment of momentum rather than a moment of hesitation.
What designers can take from this:
- Ask for user commitment after delivering value, not before
- Use a progress bar to set expectations across multi-step flows
- Let the product speak before the sign-up form does
The gamification layer, streaks, leaderboards, and daily goals are woven into every interaction rather than added on top. That is worth studying separately from the onboarding, especially for anyone building a product that needs daily engagement.
2. Revolut
The onboarding process with Revolut can be seen as a prime example of how you can successfully work through a frictional area of onboarding without having to lose the user. The required amount of personal information, as well as the requirement to pass some sort of identity verification in order to meet financial regulatory obligations, can create a large barrier to potential users. However, by focusing on one decision at a time, placing compliance copy below the fold instead of blocking the ability to continue to the next step, and providing micro copy like e.g., “Daniel, not Dan” to prevent errors before they occur, Revolut is able to make the experience feel less like going through a large set of bureaucratic forms. Furthermore, users can also access a limited view of the dashboard while their documents are being officially checked; therefore, they aren’t sitting there looking at a loading screen after submitting their identification.
The flow also handles a step that most designers underestimate: the physical card order. Revolut lets users customize their card design mid-flow, which turns a compliance-heavy process into a moment of personalization. That is a useful reminder that emotional design and regulatory requirements are not mutually exclusive.
3. Notion
Branching Onboarding Based on User Type
Notion’s onboarding branches early. After a minimal sign-up, the product asks whether the user is setting up a personal workspace or a team workspace, then displays a completely different set of templates and prompts for each path. Individual users see a simplified template gallery. Team users get introduced to shared workspaces and prompted to invite collaborators. Neither group is exposed to the complexity that belongs to the other.
What the Settings Flow Teaches
Notion’s settings screens are worth studying independently. The information density is high, but the visual hierarchy manages it well. Features are grouped by function, advanced options are accessible without crowding the primary interface, and the overall structure scales across plan tiers without requiring a redesign. That kind of settings architecture is harder to build than it looks.
4. Airbnb
The booking process of Airbnb includes two distinct types of people using the same service. One type is Guests who would like to book a place to stay, and Hosts listing the properties. As guests are searching for accommodations during their stay, the guest portion of Airbnb search has filters displayed in view and remains on screen while searching, as opposed to navigating through a menu. This dramatically decreases the time it takes to complete the search process. Airbnb also provides hosts with user-guide type step-by-step prompts, written in simple wording, to minimize the amount of time hosts have to spend determining what they will enter into the app.
What makes the booking confirmation flow worth studying is how Airbnb handles trust at the payment step. Reviews, cancellation policies, host response rates, and price breakdowns all appear before the user commits. The checkout does not rush toward conversion. It builds enough confidence that the user wants to complete the booking.
5. Stripe
Stripe’s product library on Page Flows reveals something often overlooked in most checkout discussions: how a payment product handles error states and recovery flows. The sign-up flow asks for minimal information upfront, uses a magic link for authentication to avoid a “forgot password” moment right at the start, and handles form validation inline rather than after submission. Those are well-documented best practices, but seeing them executed across a complete, real flow is more useful than reading about them.
What These Five Products Have in Common
These products were subjected to numerous tests with real-world audiences; their flows reflect actual decisions made in the real world, rather than just what would have happened in theory. Designers studying these products before creating new designs will generally ask better questions during the discovery phase, catch sequencing issues early, and incorporate concrete evidence into discussions with stakeholders. Therefore, this library does not replace any “original thought,” but does serve to ground that original thought prior to its genesis.
© Copyright 2026 – St. Louis Media LLC dba STL.News
