Base44: Build Apps with AI is a freemium development platform that creates applications from natural-language instructions. Base44 offers Android and iOS apps, a Mac app and a browser editor. It generates the interface, application logic and data model, then supplies hosting, database services and user authentication.
From instructions to a working app
Users describe the application they want, including its pages, forms and behavior. Base44 generates a working project and displays it in an interactive preview. Users can open pages and try their controls while reviewing the result. Further messages can add functionality, change existing pages or adjust how the application handles information.
The chat offers Build and Discuss modes. Build acts on the request immediately, while Discuss answers questions or develops a proposed plan. Users can inspect that plan, approve its implementation or reject it and continue the conversation. Base44 checks generated changes and fixes errors in the background.
Templates and visual changes
Base44 also starts projects from templates that its team or community creates. Choosing a template copies it into the user’s workspace for independent changes. Users can replace its content, revise its design and change its behavior. Templates that depend on backend functions require Builder or a higher plan.
Design instructions can target the entire app or one page. In the editor, the Theme panel applies colors and fonts across the project. Edit mode instead targets selected preview elements, with controls for text, color, typography and spacing. Selecting a repeating element applies the change across its matching copies.
Records, accounts and access
Base44 organizes application data into tables, with records as rows and fields as columns. Fields can hold text, numbers, dates, files or references to other tables. Users can inspect and edit records through the dashboard. Importing CSV, Excel or JSON through chat maps incoming columns to fields and appends new records without replacing existing ones.
Authentication supplies customizable login, registration and password recovery pages. Visibility settings control who can open the finished application:
| Visibility | Audience |
|---|---|
| Public | Anyone on the internet |
| Private | Invited people who sign in |
| Workspace | Workspace members who sign in |
Private apps require a paid plan. Live app roles control activity inside the application; separate collaborator permissions grant editor access. Domain and security management require the desktop editor.
Connecting services to an application
Base44 includes integrations that perform several types of work inside generated apps:
- Invoke LLM produces AI responses from prompts and supplied context.
- SendEmail delivers messages with custom sender names and HTML content.
- UploadFile stores an uploaded file and returns its URL.
- GenerateImage creates an image from instructions and optional reference images.
Connectors add services such as Slack, Notion and Google Workspace. Users request the connection through chat, sign in and approve permissions. The app can then read or write the permitted data. Connectors require Builder or a higher plan.
Workflows with triggers and steps
Base44 builds workflows from descriptions of recurring or event-driven work. A trigger starts the process, and ordered steps run backend functions, send emails, wait or branch according to conditions. Triggers can respond to schedules, changed records, connected services, publication or payments.
The dashboard displays a diagram and records each run, including successful and failed steps. Workflows require Builder or above. Some existing projects retain Automations, which execute individual backend functions, instead of Workflows.
Testing application flows
The Base44 testing agent accepts named scenarios or generates suggested tests from the application and chat history. Users select tests and run them through an automated browser session. The agent follows interactions such as submitting forms or moving between pages, then reports results.
Its Issues view identifies problems, while Activity shows the actions it took. Selecting Fix with AI sends chosen issues into chat for correction. Tests use a separate environment and leave production records untouched. The agent cannot test the login process itself.
Publishing to the web and app stores
Publishing sends the current application to Base44’s hosting and supplies a shareable web address. Users can distribute that link or let visitors add the app to their home screen. Later published changes reach those visitors automatically.
The editor also scans projects against Apple and Google store guidelines. It can generate IPA and AAB submission files that wrap the published app in a native web view. Free users can run the scan; downloading submission files requires Builder or above. Users handle submission through their own developer accounts.
Working with project code
Base44 lets paid users edit application code directly. Builder and higher plans also support two-way GitHub synchronization, so changes can move between the app editor and a repository.
ZIP export requires a computer and includes the current frontend, backend functions and data structure. It excludes records, secrets, user accounts and version history. Users export table records separately as CSV files. Exported code continues to use Base44 services for data, login and integrations; copying the project does not supply an independent hosted backend.
Traffic and application activity
Base44 starts collecting analytics when people visit a published app. The dashboard shows visits, unique visitors, visit duration and current activity. Additional views break traffic down by pages, source, location and device.
Users can choose dashboard cards, change chart types and filter traffic segments. Custom events track actions such as signups or button clicks. Paid plans add date-range choices beyond the Free plan’s available view.
Superagents across connected tools
The Base44 mobile app also provides access to Superagents. Users describe tasks, attach context and connect services through plugins. A Superagent can research information, prepare reports or act across those services, rather than operate only inside one generated application.
Text, uploaded files, images and dictated messages supply instructions and context. Scheduled or triggered workflows let the agent repeat work, while its activity view records workflow runs. Generated files appear as preview cards in the conversation.
