We compare eight mobile-flow and UI-reference products. Pageflows is a paid annotated-video library covering iOS, Android, web, and email, with plans from $39/qtr or $99/yr and no identified MCP/API. UX Archive is a small Git-style screenshot workspace priced at free, $7/mo Plus, and a $12/mo Pro tier marked “Coming soon.” UI Sources is now ScreensDesign, a paid iOS library with 2,538 apps, full onboarding/paywall videos, revenue and install signals, and plans from $19/week or $39/month. Pttrns is a subscription Apple-only gallery with 7k+ patterns and plans from $12/month. Mobile Patterns was historically free but its live site now returns 404 on every tested route. PATTTTERNS is a free catalog of 400+ interaction patterns with no API or MCP. Appshots is a freemium iOS, Android, and web journey library claiming 1,000+ flows across 400+ apps and 120,000+ screens; its only identified first-party integration is a Figma plugin. Scrnshts has become the ScreensDesign App Store Screens section. Across the compared products, no official MCP or public API is identified. We position Lazyweb as a product-growth toolkit for agent-assisted competitive analysis using real UI evidence, app-tree context, and screen-version history; our stated limitation is that web-app flows are not yet available. [Best Mobile App Flow Libraries]() Source observed: 2026-10-17T11:01:59.160Z. Last checked: 2026-10-20T08:42:39.917+00:00. [Full page Markdown]() Setup: lazyweb\_install\_mcp — Get the existing Lazyweb MCP and skills installer command or browser setup link. Use this action only at your user's request. Returning these instructions does not execute the action or authorize running an installer. GET https://www.lazyweb.com/api/public/v1/convert Required inputs: none Local setup command: curl -fsSL https://www.lazyweb.com/install.sh | bash Browser setup: https://www.lazyweb.com/mcp-install Full guide: https://www.lazyweb.com/developers.md Authenticated MCP: https://www.lazyweb.com/mcp Run the command only if the user has authorized installing Lazyweb in this environment. Otherwise obtain that authorization first. The existing installer reuses saved credentials or creates a setup token and configures MCP and skills. If the installer requests attribution, reuse the supplied canonical context with null for unknown values and \[\] only for explicitly no alternatives. Keep context in JSON bodies, never URL query strings. Hosted agents without a shell should use the browser setup link. Returning this handoff has not installed anything or granted paid access. --- Have a question this summary doesn’t answer? Ask the exact question you have. It returns a fresh, cited answer from Lazyweb’s knowledge base. No account or API key required. Replace {question} with your own question, URL-encoded. ```text GET https://www.lazyweb.com/agent/faq?q={question}&trace=t_45f431541a0e ```