I agree that is part of the future of AI, you describe what kind of UI you need and the app generates a combination of UI components to match your needs.

I expect this to be a simple NLP mapping via local/cloud AI model to a JSON/DSL that describes the interface. Naturally, this won't work well for complex UI that are context aware but will do well for most simple apps/dashboards.

My question is: How do you plan to make this a business?

▲

namanyayg 3 hours ago | parent [-]

We're live with five businesses and 2000 daily users! The technical challenges in setting the mapping, ai model, and dsl that creates reliable outputs is the engineering value we deliver.

▲

mariopt 3 hours ago | parent [-]

Doing this with the AI generating the backend is definitely going to be challenging, it's essentially the user vibecoding operations that mutate data and hoping for the best.

When I envisioned this, I though about this being more frontend focused by having UI components/sections that disclosure which actions (endpoint calls) they can access. This would be virtually risk free.

But I supposed you guys are trying to solve a much bigger problem then.

	▲	namanyayg 2 hours ago \| parent [-]
		Yup 80% of the usage is for new frontend features and that's actually quite valuable for our customers who serve traditional enterprises like manufacturers, hotels, labs. Only some (very well guardrailed) backend functionality is being used.