September 2026 Summaries

No-code AI agent builders enable users to create software that can make decisions and perform actions through visual workflows and plain-language prompts rather than programming, supporting uses such as customer support, lead qualification, content generation, research, operations, and mobile data capture. The guide presents Bubble as a platform for building complete web and native mobile applications with shared databases, workflows, hosting, deployment, privacy controls, and connections to AI models and external services through APIs, while contrasting it with tools such as Lindy and Gumloop for focused standalone agents and n8n for more technical customization. It distinguishes AI agents from conventional chatbots by emphasizing agents’ ability to trigger multistep actions such as updating records, sending notifications, processing payments, and escalating cases to people. Key selection criteria include visibility into editable logic, database security and privacy rules, integration support, human approval steps for consequential actions, deployment capabilities, and native mobile features such as push notifications and camera access.

Bubble co-founder Emmanuel Straschnov’s September AMA introduced updates aimed at giving builders more control over app creation, including exact-match file searches, a public-beta mobile plugin editor using React Native libraries, and replacements for the retiring BubbleGo testing app through browser-based simulated devices and paid-plan dev builds. Bubble’s AI Agent now supports a conversational app-generation process, live-preview editing, API Connector setup, animations, improved mobile styling, and Claude Sonnet 5, while an upcoming MCP integration will allow users to edit Bubble apps and explore app information through external AI tools such as Claude or ChatGPT. Straschnov also said workflow branching and loops are nearing release, server-side pre-rendering is under exploration for performance and SEO, and AI usage limits are being introduced with support available for affected users. He noted that Bubble apps can connect to external services through APIs, discussed ongoing mobile priorities and limitations such as offline support and biometric authentication, and announced Launch Lab winners: KlubPlus by Jesper Vestergaard received the top prize, Playbuk by Derek Duncan won best web app, and Business Class by Emile Elie and Camille Köse won best mobile app.

Bubble’s native mobile editor can be extended through a marketplace of nearly 700 no-code plugins that add device-specific capabilities and polished interface components. Five highlighted options include No-Code Venture’s Local Storage plugin, which uses MMKV for fast on-device key-value storage with optional encryption and requires developers to clear sensitive data on logout; Zeroqode’s Mobile Charts Pro, which creates customizable live bar, line, and pie charts; and its QR/Barcode Scanner, which supports camera or image-based code scanning, multiple formats, workflow triggers, and continuous scanning. Not Quite Unicorns’ free Better Audio Recorder supports MP3 recording, uploading, database storage, and recording-state workflows for features such as voice notes. Airdev’s Mobile Pack: Native Power Kit combines components including dropdowns, uploaders, gesture detection, rich-text editing, charts, video playback, scanning, and date pickers, with further additions planned. The expanding library is supported by Bubble’s public-beta plugin editor and is intended to help developers build mobile features without custom code.

Bubble’s guide explains how businesses can create custom appointment-booking websites, web applications, or native mobile apps using its AI-assisted visual development platform, offering greater control over branding, data, workflows, provider assignment, payments, and client intake than off-the-shelf tools such as Calendly or Acuity Scheduling. It outlines core capabilities including service selection, calendar synchronization with Google Calendar or Outlook, conflict detection, automated email or SMS reminders, Stripe payments and deposits, cancellation policies, provider routing, reporting, and optional AI features such as natural-language scheduling, chat-based questions, and no-show risk assessment. The recommended process begins with describing the app to Bubble AI, defining data types for users, providers, services, and bookings, designing a responsive booking interface, configuring integrations and workflows, and testing before publishing to a custom web domain or, through Bubble’s beta native mobile tools, Apple and Google app stores. The platform is positioned as most useful when businesses need complex scheduling logic, a white-labeled client experience, or booking embedded within a broader portal or CRM, though regulated use cases require separate compliance consideration and Bubble does not support HIPAA-required apps.

Bubble’s guide describes how users can build and launch no-code e-commerce websites, web apps, and native iOS and Android apps using its visual editor and AI tools. It outlines core development steps including defining business goals and customer types, creating database structures for products, users, carts, and orders, designing catalog and cart interfaces, integrating payments through Stripe or other services, establishing privacy rules, testing checkout and security, and publishing on the web or mobile app stores. The platform supports business models such as direct-to-consumer stores, marketplaces, and B2B ordering systems, while optional AI features can provide recommendations, semantic search, and generated product descriptions. The guide recommends launching first with essentials such as a catalog, cart, checkout, payment processing, order management, and accounts, then adding growth features including push notifications, wishlists, loyalty programs, reviews, analytics, and advanced search. It notes that Bubble’s free plan supports development and testing, while paid plans beginning at $59 per month are required for live deployment, alongside external costs for app-store accounts, payment processing, and domains.

Bubble’s Business of Building 2026 report analyzes observed activity from more than 250,000 live and deployed apps, including 11.9 million deploys and 233 million edits, to identify behaviors associated with earning revenue. Although apps can typically move from idea to deployment in about three days, monetized apps tend to charge early, with nearly one-third processing payments on their first day and the typical app completing a first transaction within eight days. Revenue-generating apps also receive far more ongoing development, averaging about 45 deployments, 614 edits, and activity across 46 days in their first six months, compared with two deployments, 25 edits, and four active days for apps that do not earn revenue. Apps incorporating AI features are reported to monetize more often than those without them, though such features bring higher operating costs and variable outputs. The report concludes that sustained iteration, responsiveness to paying users, and builders’ ability to understand and modify their products are more strongly associated with durable businesses than launch speed alone.

AI-generated code can accelerate application development but often prioritizes functionality over security, creating risks such as missing authorization context, SQL injection and cross-site scripting vulnerabilities, weak validation or authentication, hallucinated or outdated dependencies, and reduced human scrutiny of polished-looking output. Because models learn from public code that may contain known flaws, all generated code should be treated as untrusted and reviewed through human oversight, automated static application security testing, software composition analysis, dependency verification, secret scanning, and deployment guardrails. Protecting data also requires deliberate database permissions and row-level security, while authentication, payment, and sensitive workflows merit particularly careful review. The piece presents Bubble’s visual development environment as an alternative that makes workflows, privacy rules, data access, and AI-generated changes inspectable without requiring users to read code, alongside security-dashboard checks, shared web-and-mobile permissions, encryption, audit visibility, and SOC 2 Type II compliance.

Bubble marked its 14th anniversary with “Destination Bubble 2.0,” a company-wide Spirit Week designed to connect longtime and newer employees around the organization’s history and future. The event centered on a digital Bubble Passport app built by a non-engineer on the People team with support from a developer, allowing employees to complete activities, collect stamps, and enter prize drawings while demonstrating Bubble’s no-code mission. Activities included sharing workplace memories and AI productivity tips, nominating colleagues for values awards, participating in trivia, wearing Bubble-themed clothing, attending an All Hands toast, and taking team photos, with remote employees receiving mailed travel kits to support participation. A Slack discussion about employees’ joining years and favorite memories drew 78 responses, bringing together stories from recent hires, remote staff, and co-founder-era employees. Organizers described the celebration as both a recreational event and an effort to create a shared experience across remote and in-office teams while recognizing Bubble’s growth over 14 years.

Publishing a Bubble-built native iOS app requires a separate Apple Developer Program membership costing $99 annually, with an Apple Account using two-factor authentication, accurate legal identity information, and, for organizations, a D-U-N-S Number, matching company website, and an authorized representative. Individual accounts are generally approved faster but display the person’s legal name as the App Store seller, while organization accounts display the legal entity’s name and undergo manual verification. After approval and payment, developers use App Store Connect to assign team roles, create an app record with an irreversible bundle ID, and, for paid apps or in-app purchases, complete agreements, tax forms, and banking details. Additional iOS requirements may include push-notification credentials and an accurate privacy policy and data disclosures. The material also notes that Android distribution requires a separate Google Play developer account with a one-time registration fee, app signing, privacy information, and potentially a 14-day closed test for newer personal accounts. Bubble enables web, iOS, and Android development from one editor, helps package and validate app builds, supports TestFlight and limited over-the-air updates, but leaves store-specific accounts, credentials, reviews, and compliance obligations to the developer.

No-code Stripe integration uses Stripe’s hosted payment tools and a no-code platform’s visual interfaces to manage one-time purchases, subscriptions, invoices, and customer billing without custom API development. Businesses can select among Payment Links, Checkout, Pricing Tables, invoices, and the Customer Portal based on their sales model, then configure products, prices, payment methods, and wallet support in Stripe’s test environment before launch. Platforms such as Bubble can connect to an existing Stripe account through API keys, support hosted checkout flows and embedded pricing tables, and use visual workflows to grant access, update subscription records, send notifications, and respond to payment outcomes. Webhooks are important for tracking successful payments, renewals, failed charges, and Customer Portal changes, while Stripe Billing’s automated retry and notification features can help recover failed subscription payments. Before moving to live mode, users should verify their account, domain, webhook URLs, compliance requirements, and live API keys, test the complete purchase flow, and account for mobile app-store rules governing digital subscriptions.

No-code platforms can convert operational spreadsheets into applications that provide structured databases, mobile-friendly interfaces, workflows, auditability, and more granular security than shared files typically offer. The process begins by cleaning spreadsheet data, using clear headers, consistent column types, no merged or summary rows, unique identifiers for linked records, and separate CSV exports for each tab. Users can choose import-first tools such as Airtable or Glide for simpler applications, or generate-first platforms such as Bubble for greater control over data models, layouts, workflows, and permissions. In Bubble’s approach, AI can generate an initial app structure, help configure tables and relationships to match spreadsheet tabs and columns, import CSV data, and recreate formulas as computed fields or automated workflows. The resulting app can include list, detail, and form pages, role-based and record-level access controls, and web or native mobile publishing, with a shared database supporting all versions.

Healthcare app development spans patient-facing products such as telemedicine, portals, wellness tools, and appointment booking, as well as internal provider systems for referrals, intake, scheduling, remote monitoring, and task management. Bubble offers a no-code visual platform with AI-assisted generation, shared web and native iOS/Android backends, user authentication, workflows, role-based privacy controls, notifications, API integrations, and security checks that can help create prototypes and non-PHI healthcare tools. Common healthcare app requirements include secure login, scheduling, messaging, audit trails, permissions, reminders, and integrations with EHR systems through standards such as FHIR and HL7. Although Bubble provides SOC 2 Type II compliance and encryption at rest and in transit, it is not HIPAA compliant and should not store protected health information; PHI, clinical messaging, files, and regulated workflows should instead use HIPAA-compliant external services, with legal, compliance, and technical review.

Bubble’s native mobile in-app purchase feature enables apps to sell recurring digital subscriptions through Apple’s App Store and Google Play billing systems, which are generally required instead of processors such as Stripe for in-app digital goods. Developers must create app records, sign payment and banking agreements, configure subscription products and pricing in App Store Connect and Google Play Console, and connect matching store credentials, product IDs, and plan variants in Bubble. Bubble currently supports subscription plans, including monthly, annual, and tiered options, but not consumable credits or one-time non-consumable purchases; it validates receipts and automatically maintains subscription status, renewals, and cancellations in its read-only Subscription Purchases table. Developers use Bubble’s workflows and subscription operators to manage access entitlements, must provide a Restore Purchases action, and should configure Apple and Google billing notifications for real-time updates. Testing should begin with Bubble’s simulated flows and continue through Apple sandbox/TestFlight and Google Play internal testing before store submission, while free trials and introductory offers can be configured directly in the respective app stores.

No-code database builders enable users to create structured data systems, relationships, permissions, automations, and simple interfaces without SQL, offering more consistency and access control than conventional spreadsheets. The comparison distinguishes Airtable for spreadsheet-like collaboration, Baserow for open-source self-hosting, Stacker for external client and vendor portals, Knack for workflow-heavy internal tools, AppSheet for Google Sheets-based mobile field data collection, Xano for developer-oriented backends and APIs, and Bubble for integrated full-stack applications with AI-assisted schema creation and visual privacy controls. It emphasizes that selection should depend on data-model complexity, user roles, security and compliance needs, desired interface capabilities, technical expertise, and pricing structure, while recommending that organizations test whether a platform can accurately model record- and field-level permissions before committing or migrating data.

Row-level security (RLS) is a database-level mechanism that automatically limits which records users can view or modify according to attributes such as user identity, role, department, or tenant, preventing applications from relying solely on potentially missed access checks in their own code. It acts as an invisible filter on every query regardless of whether access comes through an app, API, reporting tool, or direct database connection, making it especially useful for multi-tenant software, role-based employee access, healthcare systems, and compliance-sensitive environments. RLS differs from table permissions, which control access to an entire table, and field-level security, which hides particular columns; these controls are typically combined to provide layered protection. Effective implementation requires policies for both reading and writing, careful handling of privileged accounts that may bypass policies, and indexes on commonly filtered fields such as tenant or owner IDs to avoid performance problems.