Hoop Dev has a Lazyweb company-library entry in Engineering, Product and Design. The entry currently contains 0 screens and no available screenshots, but identifies onboarding, signup, login, paywall, and checkout as the flow areas available for comparison. It links to Hoop Dev at [https://hoop.dev](https://hoop.dev/) and places the entry within Lazyweb’s library of 281k+ real app screens, flow examples, UI patterns, and product-design patterns. [Hoop Dev app screens & user flows]() Source observed: 2026-10-16T12:18:13.150Z. Last checked: 2026-10-16T12:18:13.15+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 ```