[Cyclone_]

I've used it for creating a template for an app. It usually creates a pretty accurate app with at least a basic UI and some interactions. The biggest issue is that once you've created the template, it's pretty tough to add some more complicated features using the AI.

[markdown]

This has been my experience also.

You gotta give it detailed instructions for everything at the start. You can't just build as you go, because every time it adds something it breaks something else.

[apwell23]

> because every time it adds something it breaks something else.

standard ai workflow

[enraged_camel]

Easily prevented with good test coverage IME. Not sure how that works in Replit though.

[joshdavham]

I've never used replit but I'm curious what types of choices the app makes when building. Like how does it decide on the architecture, backend language, frontend framework, etc? Even if the non-technical user is unaware of the tech choices being made, the AI still has to make such decisions. How does it decide?

[_heimdall]

One token at a time.

If it has detailed context of exactly what the entire app will need to do before writing any code, the first tokens will be more likely to build an architecture that works well in a language and framework that is suited for it.

If the initial context is thin on details, it will still pick an architecture, language, and framework but it may not be the best fit for the end goal. After those choices are made that just becomes more context, and it likely would never consider whether the language is now wrong and the entire codebase should be started fresh with a new language or framework.

[taejavu]

It just starts and makes it up as it goes.