Agents killed no-code builders (and made APIs even more important)

Description and use

Coding agents replaced no-code builders, enabling rapid UI generation while emphasizing the need for robust API design.

Problem

No-code builders were created to reduce frontend development effort, but they imposed a ceiling on customization and became heavy and limited as customer needs grew.

Outcome

Discontinuing the no-code builder reduced customization limits and shifted responsibility to agents and APIs, leading to more flexible UI development and stronger API design.

Workflow

• 1. Identify a custom billing UI requirement.
• 2. Use a coding agent to generate the screen based on a prompt.
• 3. Review and iterate the generated UI in an afternoon.
• 4. Deploy the UI, knowing the underlying API handles business logic correctly.

Evidence

We built one of those, a no-code builder for billing UI, and this week we killed it (for new accounts).

Source

The builder existed because writing UI was expensive, and now agents made it cheap.

Source

If more of your API's callers are agents, the shape of the API becomes the guardrail.

Source