Adalo

Provides a hosted web-based editor where users drag pre-built components (buttons, forms, lists, images, etc.) onto multiple screens, configure properties via UI panels, and define responsive layout rules. The editor compiles a single visual definition into three output formats: native iOS binary, native Android binary, and responsive web app. Uses a component-based architecture where each dragged element maps to a platform-specific native control on mobile and HTML/CSS on web, with automatic layout reflow for different screen sizes.

Provides a managed PostgreSQL database (Adalo-hosted) where users define collections (tables) and fields (columns) through a visual schema builder UI without writing SQL. Supports external data sources (Airtable, Google Sheets, Xano, REST APIs) via 'External Collections' that map API responses to app components. Data is queried and mutated through the visual action system (no direct SQL access). Includes automatic record pagination, filtering, and sorting at the component level.

Exposes REST API endpoints that allow external systems to trigger push notifications to app users. External systems authenticate with API key and can send notifications to all users, specific user segments, or individual users. Notifications are delivered through Adalo's push service (Firebase Cloud Messaging for Android, Apple Push Notification service for iOS). Enables backend systems to notify app users without building custom push infrastructure.

Provides 'Ada', an AI assistant that generates app screens, components, and logic based on natural language prompts. Users describe what they want (e.g., 'create a login screen with email and password fields'), and Ada generates the corresponding components, data bindings, and actions. Marked as Beta, indicating experimental/unreliable status. Model type, context window, and specific capabilities are not disclosed.

Allows agencies and resellers to publish apps under client brands without Adalo branding. Users configure custom app name, icon, splash screen, color scheme, and custom domain (for web apps). Published apps appear to be built by the client, not Adalo. Enables agencies to build and resell apps to multiple clients under different brands.

Allows multiple team members to edit the same app simultaneously. Users can invite team members with different roles (Editor, Viewer, Admin) that control what they can do (edit screens, manage database, publish, etc.). Includes version history to track changes and revert to previous versions. Enables teams to collaborate on app development without overwriting each other's work.

Automates the process of building and submitting native app binaries to Apple App Store and Google Play Store. User configures app metadata (name, icon, description, screenshots) in Adalo UI, and the system generates iOS and Android binaries, handles submission to app stores, and manages version updates. Claims to handle App Store review process automatically, though actual review is still performed by Apple/Google. Web apps are published to Adalo domain or custom domain with staged rollout (update live app without disrupting users).

Allows users to define app behaviors (actions) triggered by user interactions (button tap, form submission, list item selection) without writing code. Actions are composed visually: set a variable, show/hide a component, navigate to a screen, call a REST API, send an email, trigger a database query, or execute a Zapier workflow. Supports conditional logic (if-then-else) based on component state, user data, or API response. Custom Actions can call external REST APIs with configurable headers, authentication, and request/response mapping.

Integrates Stripe for one-time payments and subscriptions, and IAPHUB for in-app purchases (iOS and Android). Users configure payment flows visually: add a 'Pay with Stripe' button, define product/subscription details, and Adalo handles payment processing, webhook handling, and transaction recording. Stripe webhooks automatically update app database when payment succeeds/fails. In-app purchases are managed through IAPHUB SDK, allowing users to monetize apps without managing Apple/Google payment systems directly.

Enables sending push notifications to app users via a visual notification builder. Users define notification content (title, body, image), target audience (all users, specific user segment, or triggered by app event), and scheduling (immediate or delayed). Notifications are sent through Adalo's push service (likely Firebase Cloud Messaging for Android, Apple Push Notification service for iOS). Includes analytics on notification delivery and engagement (open rates, click-through rates).

Enables apps to access user location (latitude/longitude) and display interactive maps using Google Maps API. Users can add a Map component to display locations, search for nearby places, calculate distances, or trigger actions based on geofencing (user enters/exits a location). Location data is stored in app database and can be used for filtering (show nearby restaurants, delivery drivers, etc.). Requires user permission to access device location.

Provides built-in analytics dashboard showing app usage metrics: daily/monthly active users, screen views, user retention, session duration, and custom events. Tracks user interactions (button clicks, form submissions, screen transitions) automatically without code. Users can define custom events (e.g., 'user_purchased', 'video_watched') and view aggregated metrics in dashboard. Data is collected server-side and visualized in Adalo UI.

Enables apps to trigger Zapier workflows (automations) when app events occur (user signs up, form submitted, payment received, etc.). Users configure a Zapier trigger in Adalo action builder, and Zapier automatically executes downstream actions (send email, create Slack message, add row to Google Sheets, etc.). Eliminates need to build custom integrations with external services. Zapier handles authentication and data transformation between services.

Exposes REST API endpoints that allow external systems (backend services, third-party apps, mobile clients) to read and write data to Adalo app database collections. External systems authenticate with API key and can perform CRUD operations (create, read, update, delete) on app data. Enables Adalo apps to act as a backend-as-a-service for other applications or to sync data with external systems. API responses are JSON-formatted.