Adalo

Adalo provides a visual canvas-based editor where users place pre-built components (buttons, forms, images, lists) across multiple screens without writing code. The system automatically handles responsive layout constraints for different device sizes (mobile, tablet, web) and compiles the visual definition into native mobile binaries (iOS .ipa, Android .apk) and web applications. Components are positioned absolutely on a grid-based canvas, with styling (colors, fonts, spacing) applied through a visual property inspector rather than CSS.

Adalo hosts a managed PostgreSQL database for each app, allowing users to define data schemas (called 'Collections') through a visual interface without writing SQL. Users create tables, define column types (text, number, date, boolean, image, file, relationship), set up one-to-many and many-to-many relationships, and configure validation rules. The database is automatically provisioned, backed up, and scaled within tier limits (500 records free, 5GB Starter, 25GB Professional, 125GB Team). Data can be imported from CSV, exported as JSON, or accessed via the Collections REST API.

Adalo includes 'Ada', an AI assistant (model unknown, Beta status) that can generate UI screens from natural language prompts. Users describe a screen (e.g., 'create a login form with email and password fields') and Ada generates the visual layout with components. Ada can also edit existing screens based on prompts (e.g., 'change the button color to blue'). The AI component is included in all paid tiers but marked as Beta, indicating incomplete or unstable functionality.

Adalo integrates with Zapier, allowing external services to trigger Adalo app actions and Adalo apps to trigger external workflows. Users can create Zapier 'Zaps' that listen for events (new Airtable row, new email, form submission) and trigger Adalo Custom Actions (send notification, create database record). Conversely, Adalo apps can trigger Zapier workflows (e.g., when user clicks a button, create a Slack message). Integration is bidirectional via Zapier's webhook API.

Adalo exposes a Collections REST API that allows external services to read and write data to an app's database without using the app UI. External services can GET collections (fetch records), POST (create records), PUT (update records), and DELETE (remove records) by making HTTP requests with an API key. This enables data sync between Adalo apps and external systems (CRM, ERP, analytics platforms) or allows third-party services to populate app data. API authentication uses API keys generated in Adalo app settings.

Adalo provides pre-built 'Feature Templates' that are complete, reusable app patterns (account settings, appointment booking, task assignment, messaging, image carousel, social feeds, etc.). Users can add a template to their app with one click, and it includes all necessary screens, database collections, and Custom Actions. Templates reduce time to build common features and serve as learning examples for new users. Templates are customizable after insertion.

Adalo allows users to define 'Custom Actions' that trigger on user interactions (button clicks, form submissions) or scheduled events. Actions can chain multiple operations: make HTTP requests to external APIs, send emails via SMTP, send SMS, fetch data from connected services, and execute conditional branching based on response data. The action builder uses a visual flow diagram where each step is a pre-built action type (API call, email, SMS, conditional, etc.) with input/output mapping. No code is written; parameters are bound to app data or user input through a visual interface.

Adalo allows apps to connect to external data sources as 'External Collections' without hosting data in Adalo's database. Supported sources include Airtable (via REST API), Google Sheets (3-click OAuth integration), Xano (dedicated backend-as-a-service integration), and generic REST APIs. Once connected, external data appears in the app as if it were a local collection — users can bind UI components to external data, create forms that write back to the source, and filter/sort data. The integration uses REST API polling (not real-time webhooks) to fetch data on demand.

Adalo provides native integrations for collecting payments through Stripe (card payments, subscriptions) and IAPHUB (App Store and Google Play in-app purchases). Users can add a 'Stripe Payment' action to Custom Actions, specify amount and currency, and handle success/failure responses. For app store purchases, IAPHUB integration allows users to define in-app products (one-time purchases, subscriptions) and trigger purchase flows from the app UI. Payment processing is handled by Stripe or Apple/Google, with Adalo passing through the transaction result to the app.

Adalo provides a Notifications API that allows external services (Make, Zapier, custom webhooks) to trigger push notifications to app users. Users define notification templates in Adalo (title, body, image), then external services call the Notifications API with a user ID and template ID to send a notification. Notifications are delivered via Firebase Cloud Messaging (Android) and Apple Push Notification service (iOS). Adalo handles device token management and delivery infrastructure; users do not manage push certificates or device registration.

Adalo compiles apps to three deployment targets: web (hosted on Adalo domain or custom domain), iOS (App Store submission), and Android (Google Play Store submission). For web, Adalo generates a static/dynamic web application and hosts it or provides deployment instructions for custom domains. For mobile, Adalo generates native binaries (.ipa for iOS, .apk for Android) that users submit directly to Apple and Google app stores. The publishing process includes staged rollout for web (deploy without disrupting live users) and automatic app versioning for mobile.

Adalo provides geolocation capabilities (access device GPS) and Google Maps integration for displaying maps, markers, and location-based data. Users can add a 'Get Current Location' action to retrieve user's latitude/longitude, then display it on a map component or use it in Custom Actions (e.g., find nearby stores). Google Maps component allows displaying markers, drawing routes, and binding location data from collections. Geolocation requires user permission (iOS/Android permission prompt).

Adalo allows multiple team members to edit the same app project with role-based access control. Users can invite collaborators with 'Editor' role (can modify app) or 'Viewer' role (read-only). The number of simultaneous editors is limited by tier (1 editor free, 5 Professional, 10 Team). Collaboration is asynchronous (no real-time co-editing); changes are saved to a shared project and visible to other editors on refresh. Version history and rollback are not documented.

Adalo provides built-in analytics (Professional tier+) that tracks user behavior, screen views, and conversion metrics. Analytics dashboard shows metrics like daily active users, session duration, screen flow, and custom events. Users can define custom events in Custom Actions (e.g., 'user clicked purchase button') and track them in the analytics dashboard. Conversion optimization metrics are mentioned but not detailed.