I see page flows as a way of validating user journeys and defining features. I use it primarily to breakdown specifications from top SaaS products around how they deal with challenging flows, such as enterprise team onboarding, role-based permissions, and in-app education tours. For example, when we recently worked on our collaboration settings, I pulled together 8 Team Invite and Permission Management flows from the library to show stakeholders. As a result, the design decisions were backed-up with solid evidence and sped-up alignment drastically. The convenience of this research is wonderful, I am able to filter by pattern and industry to find exactly what I want within a few minutes. I utilize it on a frequent basis, several times a week, during discovery phases. Sharing timestamped video snippets directly in our product specifications (in tools like Confluence) ensures that engineers and designers have a single source of truth on how the interaction is expected to behave. Review collected by and hosted on G2.com.

I cant comment on customer support because I havent spoken to them. Although the library is considerable, I sometimes wish there were more examples of extremely niche enterprise backend admin panels rather than front-end user experiences. Review collected by and hosted on G2.com.

As an IT Project Manager, I have to facilitate the flow of communications between designers, developers, and business owners. Page Flows helps me with that. I do not design screens, but I need to be aware of the UX flows in order to write reasonable specs, plan work, and guide through code reviews. The videos of real user experience are extremely valuabflows le. Instead of arguing about some theoretical concepts, I just show thcan e flow of one of the companies, for example, Slack, or maybe Dropbox, and say, This is the flow we have to follow. Review collected by and hosted on G2.com.

The product works very well for its intended purpose. From an R&D point of view, I sometimes wish that it existed in such a way that you can "pin points" on videos so that you can make a list of videos that correspond to a Jira ticket or PRD list. Further, even though the app support is very comprehensive, example videos on very specialized enterprise or legacy system UIs may be difficult to locate. Review collected by and hosted on G2.com.

As the IT Project and Business Manager, Page Flows fills an extremely important gap between design inspiration and implementation feasibility. The biggest strength of Page Flows remains the carefully collated collection of user flow videos from real-life applications. This helps me immediately gauge my projects against the likes of Airbnb and Dropbox, giving me a trustworthy point of comparison to realign my design, development, and product teams. This extremely efficient filtering system enables me to immediately retrieve examples across various use cases, whether it is for the design of an onboarding process or the checkout option, thus reducing the effort required for discussions around project requirements. Review collected by and hosted on G2.com.

The tool is very inspiration- and reference-driven. As a business manager, I sometimes wish there was more quantitative data or A/B test results available that is directly tied to the flows and their potential impact on key metrics such as conversion or retention rates. Finally, while it’s great that the effects of a cross-functional flow may be well-represented by cases from consumer products, cases from very niche domains may not be so complete. Review collected by and hosted on G2.com.

For media, whose currency is attention, clunkiness spirals into lost revenue with immediate deleterious effect. We added Page Flows to our product process 18 months ago and since then, it has been integral to competitive benchmarking and rapid prototyping. When our team opted to take on a major update to the dashboard experience for paid subscribers, we didn’t start from scratch. We used Page Flows to search for “Media,” “Paywall” and “Dashboard” to immediately find annotated flows from publishers such as The Information, Bloomberg, Substack.

That allowed us to have an evidence-based critique in our kickoff meetings. We would say, “Why does this paywall modal succeed where that one doesn’t?” Our editors and commercial teams in particular were fundamentally transformed by the screen recordings – non-technical people could see, vividly, exactly what the journey is that we’re trying to recreate; it just created unparalleled alignment. It turned subjective arguments over “feel” into objective conversations about the presence of an interaction pattern that someone could see, and even shaving 30ish percent off our discovery time. Review collected by and hosted on G2.com.

The big hole here for a media company is the relative dearth of digital publishing and subscription commerce examples. There are SaaS examples, but dynamic ad placements flows, newsletter sign-up optimizations, or personalized content recommendation modules are more difficult to come by. We often borrow principles from e-commerce or streaming services.

I’d also like to see a “Media & Publishing” vertical of insights on how to get the best user experience for ad (or subscription prompt) monetization (density, prompts etc.) A feature that could compare 2-3 approaches to the same problem (like 3 different article navigation patterns) side by side would be a gamechanger for decision making. Review collected by and hosted on G2.com.

Page Flows is most useful to me when I need to conduct UX research before launching a new campaign or feature. It lets you view real-world user flows step by step, helping you understand not just the UI but the entire journey. It's especially practical for analysing onboarding and conversion flows. Review collected by and hosted on G2.com.

Sometimes it takes a bit longer to find certain specific use cases, because the filtering could be a bit more refined. Review collected by and hosted on G2.com.

But in the wild and woolly world of digital banking, intuition is not a strategy. And when our executive team establishes a strategic goal (e.g., “simplify loan applications to increase approval rates while continuing to correctly assess risk” or “rehank the security settings dashboard for better clarity and control”), we need some common ground, grounded in evidence on which to make those decisions together. For the past two years, Page Flows has been this strategic deep-freeze at an executive level.

but I'm not designing with it on the daily. My product and design teams do. I use it for strategic reviews, at board discussions and in risk committee meetings. For instance, when we decided to invest millions in revamping our account opening flow once more to minimize abandonment further, I told the team to use Page Flows as a benchmark against top 10 fintech and neo-bank experiences. Being able to show [the board] was hugely powerful – evidence of best practice available with illustrations and annotations – de-risked the investment, which expedited approval. It turns subjective arguments about “what feels good” into objective conversations about what can be proven to have worked for users in heavily regulated, high-stakes industries. Review collected by and hosted on G2.com.

The first and most obvious disconnect we’re seeing is that there is no cause-effect relationship between business or compliance outcomes and UX patterns, as evident from the suits. I can walk through with you how a top bank constructs from scratch its terms of service, but I cannot get into the weeds on what that presentation translated to in terms of consent rates or regulatory audits and fights with customers. Also, if you included anonymized performance data (like “flows with this pattern saw X% more completion”) it would move from being a design library to a strategic business intelligence asset.

Furthermore, while there are financial services use cases out there I'd really like to see a "Financial Services & Compliance" column constructed which represents flows that are for complex disclosures, KYC steps, fraud alerts and any other experience that is special about in our world of high regulated industry. Review collected by and hosted on G2.com.

Compliance can never be an afterthought tacked onto a finished product in fintech; by the time you reach your first wireframe, it needs to have been designed into the user journey. Page Flows has been my life line to the Product team for a year+. When reviewing concepts for a new EDD questionnaire or a SAR flagging flow, high-level feedback does not help.

Instead, I sort through Page Flows's filters to find examples tagged "Finance," "Onboarding" and "Data Forms." I can show our designers precisely how top neobanks and finance apps leverage progressive disclosure, clear microcopy lines and contextual help to take the sting out of obtuse compliance steps. For example, by learning how a leading app captures beneficial ownership information, we refactored our business account onboarding and increased its completion rate by 22% while enhancing the quality of data used in our AML checks. I can’t give enough credit to annotated screen recordings — they allow me to find individual interactions that decrease user friction and drop offs through compulsory compliance steps. Review collected by and hosted on G2.com.

The most relevant gap is the absence of flows that demonstrate highly specificity of regulatory or back-office compliance interfaces. I have to design, and also review internal tools of case management, alert triage and audit trails but i see very few examples out there. We often infer from SaaS admin panels.

Similarily, good as the library is for how to ask a question, I think it would be beneficial if there was more best-practice research or commentary on the regulatory psychology of things - e.g., how phrasing affects truthful response and layout accuracy in data for OFAC checks. This would make it more obtainable than a model reference, as would then be turned from a design specimen into an actual compliance-design manual. Review collected by and hosted on G2.com.

Proof, not promises You need proof, not just promises. In discussions with big-box retailers, I’m frequently asked about how we stand behind our products outside of the traditional marketing sense. Six months ago, I began building a new part of my sales deck with Page Flows - a "Digital Excellence" showcase. I”m not doing design on it, I’m using it for competitive intelligence and strategic storytelling.

For instance, in preparing for a review with a national grocery chain, I was able to instantly load on the customer onboarding flows of two industry leading beverage brands through Page Flows. With real, annotated examples of the two products side by side, I could show our buyer that not only does our product sell to its market better than anything else out there but also that our website and mobile experience are more intuitive, modern and designed for higher conversion than anything else on the market. This is visual proof that enables us to ask for better shelf placement or promotional endcaps, positioning Olipop as a forward-thinking digitally-native brand. The searchability is key for a non-designer like me: I’m able to find these great examples in minutes. Review collected by and hosted on G2.com.

The biggest hole from a sales enablement perspective, is the absence of CPG (Consumer Packaged Goods), or direct-to-consumer subscription commerce. Most of the examplesSo are from SaaS or tech. I will frequently pull tactics from retail or e-commerce sites. I would also appreciate a "Sales Enablement" template or tag of flows which are particularly helpful to show off UX maturity for non-technical business people (eg retail buyers). Review collected by and hosted on G2.com.

My role at my company, as a Junior Account Manager is to serve as the voice of our VIP clients and also wine club members. When something isn't working or if they have a feature to recommend on our website and account portal, then I’ve got to translate their feedback into things we can do for design and/or web development. It was difficult before Page Flows, I could describe problems but solutions were hard to explain.

Today, I use Page Flows once a week at least. For example, when multiple users noted that the gift-configuration flow was confusing around the holidays, I searched for “gifting” and “multi-step forms” on Page Flows. Within a few minutes, I had found example implementations from leading retailers with obviously misleading progress indicators and lack of error prevention. Around those, I could send these direct links to our product team with my notes, so we shared that visual understanding. This has had a huge impact on our internal communications and the time to get client-requested features released. Review collected by and hosted on G2.com.

Great library but as a premium wine/gifting company(we sell direct online), I wish there were more curated examples from high-end retail / club membership platforms or subscription services that are closer to our business model. I’m always borrowing ideas from larger-scale e-commerce sites. Also, the search is great - but a 'save' or 'collections' feature for flows I need and use is going to save me time. Review collected by and hosted on G2.com.

In a B2B SaaS startup, every product decision is full of risk. A terrible user interface can literally churn users. Over the last year, Page Flows is my tool of choice when putting our product planning and feature design sprint plans. More recently when we redesigned our main "Request for Quotation (RFQ)" module (a highly complex multi-step workflow), our team of designers heavily leaned on Page Flows.

We turned to the advanced filtering on a daily basis, seeking out examples under “SaaS,” “Dashboard” and “Data Tables” to learn how leading platforms such as Asana and Airtable package complex data in a coherent way. As biz-side CEO without design, annotated screen recordings allow me to quickly understand why these (or other) UX patterns work so I can give meaningful feedback. For instance, we embraced a particular pattern of > that we saw and our user testing justified could save 20% completion time. It's such an easy-to-use tool, it democratizes design thinking throughout the entire leadership team. Review collected by and hosted on G2.com.

As a SaaS founder, the biggest constraint holding you back is the distance between being inspired and having clarity around execution. I can understand what Slack does when for onboarding, but it would be a life-changer if you could explain those front-end components or React libraries to accomplish the same. That should accelerate the evolution of design into our engineering team.

Also, while the library is full of consumer apps, I would like more examples about deep enterprise B2B workflows like configurable admin panels or showing audit log interfaces that are crucial for our product. It's an investment that should be made, although early startups might find the cost prohibitive (Nothing some sort of "startup plan" with at least 50k free can't fix..). Review collected by and hosted on G2.com.