Feature Requests

It would be super useful to have support for variables, similar to what Figma offers. Being able to attach specified values to things like padding, gap, or basically anywhere that allows a numerical input would enable a lot of systematic structure that's currently not natively possible. It could work similarly to how text style sizing works, where its possible to define a size based on the breakpoint. Variables could allow for a layer of abstraction in defining consistent system-wide values, such as "padding-large" being set to 128px on desktop and 64px on mobile, for example. This would make updating values across all pages much easier.

When a shared component library is used across multiple projects, updates currently have to be applied one component at a time in each project. Adding an “Update all components” button (or a centralized update manager) would let users apply library updates in bulk, saving time and reducing missed updates.

I found that there's no any options to translate the component text content inside the CMS. It will be great to have a locale support for CMS components. Thank you.

I know we have the option to create multiple styles, but in some cases, it is nice to set a custom font weight different from that style for individual words or paragraphs. It’s the same as we usually do with colors, which in most cases will be different from the style color since it is common that the same size of font appears in multiple colors.

I began using Base44 to construct a site. I was extremely happy with the AI interface as I am not technically versed in any website building. I have a vision for a platform and I was able to design the homepage I wanted. Chat GPT created a prompt to give to your AI to begin rendering my design in your platform. You cannot paste the prompt in your AI tool. Furthermore, you cannot integrate access from Chat GPT to your AI. These are both needed improvements for novice web builders.

1.Duplicate Funnels Add the ability to duplicate existing funnels. This would make it much faster to create new variations or experiments based on an existing funnel setup without rebuilding everything from scratch. 2.Pause / Draft State for A/B Test Variants Allow A/B test variants (e.g., Variant B) to be set to a paused or draft state. This would allow teams to prepare experiments safely without the risk of unfinished variants going live, especially in environments where multiple team members may publish updates at the same time

A centralized media library where users can upload images, videos, Lottie files, and other assets once and reuse them anywhere across the site without needing to re-upload or re-import the same file multiple times. This library would act as a single source of truth for all media. Any asset stored in it could be referenced throughout pages, components, CMS items, and overrides. Updating the file in the library would update it everywhere it’s used, keeping projects lighter, consistent, and easier to manage.

When we need to create responsive variants with some functionality, variant count goes out of hand since we need to recreate the functionality for each breakpoint. If there was a way to control breakpoints in components separately from functionality, we would would dramatically reduce the number of variants and it would be much easier to update the functionality later once instead of having to remember to update it for all other breakpoints.

Visualize where users click/tap on a published site Show scroll depth across all breakpoints Display interaction hotspots

Ability to publish specific CMS items and standalone pages (instead of the whole site), as well as scheduling deploys for a later date.