Prompt build and prompt edit are separated.
Some tools can generate a first version from a prompt but still rely on visual editing or code for deeper changes.
Capability map
What each app builder can actually do
This page turns the source feature notes into buyer-facing capability lanes: build flow, app foundation, growth stack, transaction support, and edge use cases.
Database, forms, and multi-user support matter together.
A tool is more app-ready when it can store data, collect responses, and support user-specific workflows.
SEO, analytics, tests, and ads reveal launch readiness.
Marketing features are uneven: many builders can publish, but fewer include experimentation or ad tooling natively.
Capability lanes
Read the tools by job, not by checkbox count
These lanes are generated from the feature evidence and keep the tool list alphabetical inside each lane.
Prompt-built product
Tools that can start from a prompt and support real app workflows.
Business app platform
Tools that lean toward portals, forms, internal apps, and multi-user workflow software.
Code ownership workflow
Tools that make sense when the output should live closer to code and developer handoff.
Public site system
Tools whose feature set points more toward public websites and SEO-led publishing.
Evidence grid
Compact capability evidence
Use this grid when you need the raw yes, partial, external, or not-found signal behind each lane.
| Tool | Data layer | User apps | Prompt build | Prompt edit | Search | Analytics | Experimentation | Ads | Commerce | Forms | Games |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Base44Prompt-built product | ✓Native | ✓Yes. Auth and permissions make multi-user apps possible. | ✓Yes. | ✓Yes. | ✓Native | ✓Native | -No | +Third-party | ✓Official | ✓Yes. Form-driven apps can save responses to the built-in data layer. | ✓Yes for casual/simple web games and interactive experiences. |
| BoltBusiness app platform | ✓Native | ✓Yes. Multi-user flows are possible with database and auth support. | ✓Yes. This is a core use case. | ✓Yes. Existing projects can be refined with follow-up prompts. | ◐Partial | ✓Native | -No | -No | ✓Official | ✓Yes. You can build forms and save responses using the database/auth stack. | ✓Yes for simple browser and lightweight app-style games. Not a full game-development engine. |
| BubbleBusiness app platform | ✓Native | ✓Yes. User accounts, privacy rules, and workflows support multi-user apps. | ✓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. | ✓Native | -No | -No | +Third-party | ◐Partial | ✓Yes. Forms and workflows can store submissions natively. | ◐Limited. Simple browser games are possible, but Bubble is not ideal for game-heavy apps. |
| CursorCode ownership workflow | +Third-party | ✓Yes if you build it, but Cursor is not what gives you that capability. | ✓Yes. Cursor can generate code and implementation plans from prompts. | ✓Yes. Prompt-based editing is one of its strengths. | +Third-party | +Third-party | +Third-party | +Third-party | +Third-party | ✓Yes if you build the app and storage yourself. | ✓Yes if you code them, but Cursor is just the editor layer. |
| Div-idyPrompt-built product | ✓Native | ✓Yes for database-backed tools and multi-user style web apps, though the exact auth depth is less documented than larger platforms. | ✓Yes. | ✓Yes. | ✓Native | ✓Native | ✓Native | ✓Native | -No | ✓Yes. Forms can save submissions to the built-in database. | ✓Yes for browser games and game-like experiences. |
| Firebase StudioBusiness app platform | ✓Native | ✓Yes. Firebase Auth and database services support real multi-user apps. | ✓Yes. | ✓Yes. | ◐Limited | ✓Native | ✓Native | +Third-party | +Third-party | ✓Yes. | ✓Yes for web and mobile games built on app frameworks; not a game engine. |
| LovablePrompt-built product | ✓Native | ✓Yes. Built-in auth and backend services make multi-user apps realistic. | ✓Yes. Prompting is a core workflow. | ✓Yes. You can continue editing and extending a project with follow-up prompts. | ✓Native | ✓Native | -No | -No | ✓Official | ✓Yes. Form-based apps and surveys can save responses to the built-in backend. | ✓Yes, but mainly simple browser games, quizzes, and simulations. It is not a specialized game engine. |
| ReplitCode ownership workflow | ✓Native | ✓Yes. Replit is flexible enough for true multi-user web apps. | ✓Yes. Agent can generate apps from natural-language instructions. | ✓Yes. You can keep using Agent to change the app after generation. | -No | ✓Native | -No | +Third-party | -No | ✓Yes. Easy to build with built-in database and deployment. | ✓Yes. Browser games and multiplayer web experiences are realistic, especially because you control the code. |
| RetoolBusiness app platform | ✓Native | ✓Yes. Multi-user business apps are a core use case. | ✓Yes. Retool AI can create apps from scratch. | ✓Yes. Existing apps can be edited with AI assistance. | -No | -No | -No | -No | -No | ✓Yes. Retool Forms can collect and store responses. | -No. |
| SoftrBusiness app platform | ✓Native | ✓Yes. Portals, permissions, and user groups are a core strength. | ✓Yes. AI Co-Builder can generate apps from prompts. | ✓Yes. Prompt-based changes are supported. | ✓Native | ✓Official | -No | +Third-party | -No | ✓Yes. | -No or not ideal. Softr is much more a business app platform than a game platform. |
| v0Code ownership workflow | ✓Official | ✓Yes, but only once you set up the necessary auth/backend pieces. | ✓Yes. That is the main entry point. | ✓Yes. Prompt-based iteration is a core workflow. | ◐Partial | ✓Native | ✓Native | +Third-party | -No | ✓Yes, if you connect a database or backend service. | ✓Yes for simple web games. It is still a web-app generator, not a dedicated game engine. |
| WebflowPublic site system | ✓Native | ◐Limited/partial. User Accounts and memberships exist, but full SaaS-style app logic is not the core product. | ✓Yes. Webflow AI can generate sites from prompts. | ◐Partial. AI helps, but visual editing remains central. | ✓Native | ✓Native | ✓Native | +Third-party | ✓Native | ✓Yes. Forms can save submissions, but Webflow is not a full survey platform or app backend. | -No. |
Capability map FAQ
What does Native mean in the capability map?
Native means the feature is built into the platform or is clearly first-party according to the report's interpretation rules.
What does Official mean in the capability map?
Official means the capability is supported through an official integration or tightly supported ecosystem feature, even if it is a separate service.
What does Third-party mean in the capability map?
Third-party means the capability usually requires an outside product, plugin, script, or manual setup.
What does Partial or Limited mean in the capability map?
Partial means the capability is possible but not fully native end to end. Limited means it works only in narrower scenarios or is not a core strength.