Help Center

Improved

Fixed

base44

In Review

Planned

In Progress

Completed

Rejected

High Priority

Low Priority

The official Base44 roadmap - submit ideas, upvote features and track what’s planned. The content outlines Base44’s general product direction for informational purposes only. It is not a commitment to deliver any features or functionality and should not be relied on for purchasing decisions. All items are subject to change at Base44’s sole discretion.

Backlog

Next up

Done

Feature Roadmap

This is the Base44 Integration Roadmap. Suggest and upvote integrations you'd like to see supported in our platform. Whether it's a data source, plugin, or workflow tool — your input helps guide what we build next. Follow along to track upcoming, active, and recently added integrations!

Future Requests

Integration Roadmap

Hey {name|there}! 👋

The SDK writes <code>base44_analytics_session_id</code> to localStorage on <code>createClient()</code>, before any consent check can run. Hiding the Platform Badge doesn't stop it, and lazy-initialising the whole client breaks the app since all data calls depend on it. Please add a way to gate ONLY the analytics session write behind user consent (a consent-mode flag or lazy analytics init), without delaying the rest of the SDK. This is a real requirement for EU/UK apps under GDPR/PECR.

Consent-mode / lazy analytics init for GDPR-PECR compliance

Belfast Web Studio

Base44

Consent-mode / lazy analytics init for GDPR-PECR compliance

Subscribe to post

Subscribe to post