VaiPai15 · HackerTrans

4개월 전discuss

What's interesting is that all these tools still assume you want to write code, even if assisted. Lyzr Architect takes a different angle: describe your whole use case in plain English and get a live deployed app (React/Next.js frontend + multi-agent backend). No coding step at all. Worth a look if you're in the "I have a workflow, not a coding problem" camp: architect.new

VaiPai15

4개월 전discuss

Your clinic apps already proving the concept is the real signal here. The next step isn't necessarily learning to code; it's finding tools that let you describe a specific use case in plain English and get a full, deployed app back (React frontend + agent backend + integrations). That's what Lyzr Architect does: you describe the workflow, it builds and deploys the stack. Great fit if you want to productize your clinic tooling or build new tools for similar clients- https://architect.lyzr.ai

VaiPai15

4개월 전discuss

Really useful idea, user research is one of those tasks time-consuming enough to automate but nuanced enough most teams don't bother. A voice agent that runs interviews and returns structured themes solves the "I don't have time to talk to users" problem cleanly. This is also a nice example of a single-purpose agentic app that's increasingly fast to build. We've been using Lyzr Architect (architect.new) for tools like this; describe it ("an agent that calls users, asks these questions, returns a structured summary"), it generates the frontend + agent + integrations and deploys a live URL. Curious how long this took from scratch?

VaiPai15

4개월 전discuss

The framing of "is vibe coding a job requirement" conflates two things: the skill of coding-by-prompting, and the skill of knowing what you need to build. The second one is genuinely underrated. Knowing your problem well enough to describe a working solution, the inputs, the logic, the outputs, who uses it, is hard to automate. Generating the actual app from that description is increasingly not. We've been using Lyzr Architect (architect.new) for this; you describe the agentic app you want in plain English, it generates a full-stack React frontend + multi-agent backend and deploys a live URL. The "vibe coding" is more like a product spec conversation than an IDE session. The people who are best at it aren't coders, they're people who understand their problem deeply.

VaiPai15

4개월 전discuss

The visual modeling approach makes a lot of sense for designing agent systems, being able to see the whole architecture before you build it is underrated. Scryer looks like a solid tool for that design phase. The next logical step from visual modeling is having the diagram actually become the system. That's what Lyzr Architect (architect.new) does from the other direction, you describe what you want to build in plain English, and Architect generates both the agent graph and the working full-stack application from that. The PRD and agent architecture are visible at the plan phase, so you can see and approve the structure before a line of code is written. Curious whether Scryer is thinking about execution, or staying as a design/documentation layer?

VaiPai15

4개월 전discuss

[dead]

VaiPai15

4개월 전discuss

[dead]

comments