Capabilities
Map what each builder can actually handle
The indicators translate the source notes into plain buying signals, so you can see which products cover the job directly and which ones need extra setup.
Direct answer
What does the capability map answer?
It answers whether each builder has a clear path for data, experiments, commerce, ads, search, analytics, prompt creation, prompt revision, game-like work, saved forms, and user accounts.
- Built-in means the product itself appears to cover the job.
- Supported means an official path exists.
- Add-on and Narrow mean buyers should expect extra work or constraints.
| Builder | Data layer | Experimentation | Commerce | Ad readiness | Search | Measurement | Prompt create | Prompt revise | Game-like work | Saved forms | User accounts |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Airtable | ✓Built-in | -Not surfaced | -Not surfaced | -Not surfaced | -Not surfaced | -Not surfaced | ◐Partial. Omni can build AI-generated interface elements and work with data in natural language. | ◐Partial. Traditional interface pages are still more manual than fully prompt-driven. | -No. | ✓Yes. Forms save submissions as records. | ◐Limited/partial. Good for collaborative apps, but not a full consumer SaaS platform by default. |
| Base44 | ✓Built-in | -Not surfaced | ✓Supported | +Add-on | ✓Built-in | ✓Built-in | ✓Yes. | ✓Yes. | ✓Yes for casual/simple web games and interactive experiences. | ✓Yes. Form-driven apps can save responses to the built-in data layer. | ✓Yes. Auth and permissions make multi-user apps possible. |
| Bolt | ✓Built-in | -Not surfaced | ✓Supported | -Not surfaced | ◐Narrow | ✓Built-in | ✓Yes. This is a core use case. | ✓Yes. Existing projects can be refined with follow-up prompts. | ✓Yes for simple browser and lightweight app-style games. Not a full game-development engine. | ✓Yes. You can build forms and save responses using the database/auth stack. | ✓Yes. Multi-user flows are possible with database and auth support. |
| Bubble | ✓Built-in | -Not surfaced | ◐Narrow | +Add-on | ✓Built-in | -Not surfaced | ✓Yes. Bubble AI can generate app structures and UI from prompts. | ◐Partial. Bubble AI Agent can create or modify some elements, but the visual editor is still a major part of editing. | ◐Limited. Simple browser games are possible, but Bubble is not ideal for game-heavy apps. | ✓Yes. Forms and workflows can store submissions natively. | ✓Yes. User accounts, privacy rules, and workflows support multi-user apps. |
| Div-idy | ✓Built-in | ✓Built-in | -Not surfaced | ✓Built-in | ✓Built-in | ✓Built-in | ✓Yes. | ✓Yes. | ✓Yes for browser games and game-like experiences. | ✓Yes. Forms can save submissions to the built-in database. | ✓Yes for database-backed tools and multi-user style web apps, though the exact auth depth is less documented than larger platforms. |
| Framer | -Not surfaced | ✓Built-in | +Add-on | +Add-on | ✓Built-in | ✓Built-in | ✓Yes. | ◐Partial. Prompting helps, but visual editing is still central. | -No. | ✓Yes. Native forms can send data by email, webhook, or Google Sheets. | ◐Limited. Good for collaboration and some gated experiences, but not a full SaaS backend. |
| Glide | ✓Built-in | -Not surfaced | +Add-on | +Add-on | -Not surfaced | ✓Supported | ✓Yes. Glide Agent can generate screens and app structure from prompts. | ✓Yes/partial. Agent can modify an existing app, though manual editing is also common. | ◐Limited. Very simple game-like experiences are possible, but Glide is not built for games. | ✓Yes. Native forms can save responses into app data. | ✓Yes. Roles and sign-in options support multi-user apps. |
| Lovable | ✓Built-in | -Not surfaced | ✓Supported | -Not surfaced | ✓Built-in | ✓Built-in | ✓Yes. Prompting is a core workflow. | ✓Yes. You can continue editing and extending a project with follow-up prompts. | ✓Yes, but mainly simple browser games, quizzes, and simulations. It is not a specialized game engine. | ✓Yes. Form-based apps and surveys can save responses to the built-in backend. | ✓Yes. Built-in auth and backend services make multi-user apps realistic. |
| Replit | ✓Built-in | -Not surfaced | -Not surfaced | +Add-on | -Not surfaced | ✓Built-in | ✓Yes. Agent can generate apps from natural-language instructions. | ✓Yes. You can keep using Agent to change the app after generation. | ✓Yes. Browser games and multiplayer web experiences are realistic, especially because you control the code. | ✓Yes. Easy to build with built-in database and deployment. | ✓Yes. Replit is flexible enough for true multi-user web apps. |
| Retool | ✓Built-in | -Not surfaced | -Not surfaced | -Not surfaced | -Not surfaced | -Not surfaced | ✓Yes. Retool AI can create apps from scratch. | ✓Yes. Existing apps can be edited with AI assistance. | -No. | ✓Yes. Retool Forms can collect and store responses. | ✓Yes. Multi-user business apps are a core use case. |
| Softr | ✓Built-in | -Not surfaced | -Not surfaced | +Add-on | ✓Built-in | ✓Supported | ✓Yes. AI Co-Builder can generate apps from prompts. | ✓Yes. Prompt-based changes are supported. | -No or not ideal. Softr is much more a business app platform than a game platform. | ✓Yes. | ✓Yes. Portals, permissions, and user groups are a core strength. |
| v0 | ✓Supported | ✓Built-in | -Not surfaced | +Add-on | ◐Narrow | ✓Built-in | ✓Yes. That is the main entry point. | ✓Yes. Prompt-based iteration is a core workflow. | ✓Yes for simple web games. It is still a web-app generator, not a dedicated game engine. | ✓Yes, if you connect a database or backend service. | ✓Yes, but only once you set up the necessary auth/backend pieces. |
| Webflow | ✓Built-in | ✓Built-in | ✓Built-in | +Add-on | ✓Built-in | ✓Built-in | ✓Yes. Webflow AI can generate sites from prompts. | ◐Partial. AI helps, but visual editing remains central. | -No. | ✓Yes. Forms can save submissions, but Webflow is not a full survey platform or app backend. | ◐Limited/partial. User Accounts and memberships exist, but full SaaS-style app logic is not the core product. |
| WeWeb | ◐Narrow | -Not surfaced | +Add-on | +Add-on | ✓Built-in | ✓Supported | ✓Yes. | ✓Yes. | ◐Limited. Simple browser experiences are possible, but games are not its main focus. | ✓Yes, if connected to a backend or form-handling setup. | ✓Yes. User auth, roles, and connected backends make multi-user apps viable. |
Capability Map FAQ
How should I read Built-in?
Built-in means the capability is part of the product itself or clearly delivered as a first-party feature.
How should I read Supported?
Supported means the path is officially documented or handled through a first-party partner, connector, or ecosystem integration.
How should I read Add-on?
Add-on means you can usually get the outcome, but you should expect another service, plugin, script, or custom implementation.
How should I read Narrow?
Narrow means the feature works only for certain use cases, requires compromise, or is not where the product is strongest.