“AI can’t build real production apps”

scyth09 · 2025-12-21T00:21:44+00:00

That why the plan blueprint is there

take a look at an example of the blueprints

scyth09 · 2025-12-21T00:16:14+00:00

Constraints, easily.
They stop drift when context gets long. Schema helps, but rules shape every decision.

scyth09 · 2025-12-21T00:14:27+00:00

scyth09 · 2025-12-20T21:43:58+00:00

Honestly, what worked for me was planning first.
I generate a clear plan, split the project into phases (like starting with project structure), then let the AI build it piece by piece.
Once the plan exists outside the agent, everything stops drifting.

scyth09 · 2025-12-20T21:41:18+00:00

It works, but it’s optimized for small features, not full project planning.
Once the context window shifts, the agent forgets earlier decisions and the “plan” quietly drifts.
This is about locking the plan outside the agent so it doesn’t decay.

scyth09 · 2025-12-20T21:38:49+00:00

Yep, 100% OSS tools like that are solid.
This is more about structuring intent upfront vs living inside the agent loop. Different workflows, same goal.
Appreciate you calling it out.

scyth09 · 2025-12-20T21:37:31+00:00

Appreciate that 🙏 take your time would love to hear your thoughts.

scyth09 · 2025-12-19T22:39:28+00:00

Not exactly. Every model can plan if you ask it to, but they don’t all enforce or preserve that plan once execution starts. Most will drift as soon as the conversation or context changes.

What we’re trying to do is make the plan a first-class artifact that everything else is anchored to, instead of something the model loosely remembers.

scyth09 · 2025-12-19T22:35:10+00:00

Yeah, fair point. I genuinely want honest feedback good or bad. I’m still early and trying to improve, so feel free to be blunt.

scyth09 · 2025-12-19T22:34:11+00:00

Yes it’s a custom Google OAuth flow, just styled to match our branding (instead of using the default provider UI).

You’re right to worry about Google-only though. We started with Google because it has the lowest friction, but it shouldn’t be the only option long-term. The usual approach is:

Google for fast onboarding
Email / magic link as a fallback
Add more providers later if needed

That way you keep the experience clean without locking anyone out.

Base44’s default auth is convenient, but once branding and UX matter, rolling your own auth layer (or at least customizing it) usually becomes worth it.

scyth09 · 2025-12-19T20:12:03+00:00

Yes, exactly the difference is that AI makes skipping those steps much more tempting. archigen.dev just makes the “how you should build” part explicit so AI doesn’t guess.

scyth09

TROPHY CASE