Site inspiration & templates / User-flow reference
Page Flows
Study the steps between screens.
Understand the resource
What it is.
Page Flows organizes recorded product journeys into a browsable reference library for websites and apps. A recording lets you inspect the order and presentation of a past interaction, but it cannot establish the current product's behavior, accessibility or success rate.
When it is useful
A multi-step flow cannot be understood from a single screenshot.
A proposed application
Put it to work.
This example illustrates a possible use. The proposed workflow and expected result are separate from the bounded checks recorded below.
Try this
Map a recorded onboarding sequence, note its date, and add questions about exits, permissions and error states that the recording does not show.
Result to aim for
A dated flow outline and a list of states to validate in your own product.
Before you start
What you need.
- A browser and a specific journey to study; some library features have account or paid-access boundaries.
- Check the recording date and product context before using it as a design reference.
The practical boundaries
What to watch for.
- A successful recorded path may omit errors, permissions, uncommon states and accessibility behavior.
- The sampled recording briefly encountered a decode error before a successful fresh retry; full-length and member-only playback were not tested.
Review record
What we could establish.
- Public Web navigation and a Claude onboarding recording labeled July 2025 were accessible. The first short playback attempt ended with a decode error after about 1.96 seconds; a fresh retry played about 4.49 seconds without an error. No account or collection write was performed.
The source-review notes describe documentation and identity. The account-free evaluation below records exactly which public interaction or local fixture was checked, what happened, and what remains untested.
Check current access, terms, licensing and data handling before using a resource with your own material.
Runtime and security evaluation
What the evaluation covers.
Public catalog navigation and short sample playback were confirmed. One brief decode failure preceded a successful fresh retry, so playback reliability remains a limitation.
Methods: Public HTTP response · Public browser sample · Source review. A completed check covers the stated sample; it is not a safety certification.
- Target
- https://pageflows.com/
- Version or capture
- Unversioned public page observed 2026-10-19
- Integrity scope
- SHA-256 47f2b4bed9f12a3899c070365a158f31a79a0f330590eeeda1f8c0eb63465d29 of one initial HTML response (239947 bytes). This does not fingerprint the entire application or its dependencies.
Test conditions
- Windows; Chrome 155.0.8059.82 headless via Playwright, fresh isolated contexts with a 1365 × 900 viewport.
- Reduced motion requested. GET/HEAD requests allowed; other methods and WebSocket connections blocked.
- No owner browser profile, account, credentials, purchase, upload, private fixture or service write.
Individual checks and observations
Web catalog navigation
passPublic browser sample: Follow the public Web link from the homepage.
Observed: The browser reached /web/ with product, screen, UI-element and flow browsing controls.
Initial short playback
failPublic browser sample: Open the public Claude onboarding recording and play it muted for about 2.5 seconds.
Observed: Playback advanced about 1.96 seconds, then paused with media error code 3 (decode).
Fresh playback retry
passPublic browser sample: Open the same recording in a fresh context and play for about 4.5 seconds.
Observed: Playback reached 4.49 seconds with readyState 4, paused false and no media error; media range requests returned HTTP 206.
Full recording and member features
not-runPublic browser sample: Watch the complete recording or use login, trial, save or collection controls.
Observed: Only short public playback was sampled; the full 165-second recording and account features were not tested.
Security findings and boundaries
Public catalog navigation, a short public video sample, response headers and passive request observations.
Observed · info
Playback and third-party requests
The video was served from pageflows.com. The public page also requested CDN, Lottie and analytics-related origins; non-GET telemetry and verification requests were blocked.
Practical advice · caution
Avoid mistaking a recording for a live audit
Use the recording date and context when drawing conclusions. A historical demonstration does not validate the original product's current privacy, permissions or accessibility.
Practical caveats
- The successful retry narrows the first failure to an intermittent sample result; it does not prove full-length or cross-browser reliability.
- The July 2025 label describes the reference recording, not a test of today's Claude product.
What remains untested
- No full recording, member collection, trial, sign-in or saved-content workflow.
- Playback was sampled in one browser version under a write-blocking guard; reliability and accessibility remain unbenchmarked.
Security limits
- Passive public-page observations and the stated bounded sample only; no exploitation, authenticated authorization, backend, retention or comprehensive dependency audit.
- Request blocking changes application behavior; no secure/safe certification is implied.
Evaluation sources
Follow the evidence
Sources and further reading.
Keep exploring