Over the last two weeks, we have been working on improvements to the platform. This blog post provides a simple list of what has been changed and updated and what bugs have been fixed. You can read more about the release notes here.
Pages
New features
1. Updated Color and Spacing option types
We have updated the Color and Spacing option types. The option types have been updated to enhance visual clarity and to add an even greater option flexibility which empowers more precise and personalized design control.
Color option - What has changed?
- New color picker - We’ve replaced the traditional dropdown with a visual color picker, making it easier to explore and select the exact color you need.
- Theme color previews - We now show a preview of the color directly in the color picker and in the options sidebar, so you can instantly see the color.
- Custom color selection - Take full control of your design with support for custom colors. Enter your own hex codes or fine-tune it directly in the picker.
Spacing option - What has changed?
- Updated look and feel - We’ve refreshed the interface with a cleaner, more consistent polish.
- Individual side spacing control - Fine-tune your spacing with precision: you can now set individual spacing values for top, right, bottom, and left—giving you full control over element positioning.
2. Updated Filter component option
We have updated the Filter component option. While the primary focus of this update was a technical refactor, we've also taken this opportunity to update the UI and UX—making it a bit easier and more intuitive to define filters.
Filter option - What has changed?
- Updated option UI: The option look and feel in the options sidebar has changed from a filled turquoise to a clean white look, with a new, dedicated filter-supportive button.
- Wider filter modal: The default max width of the modal has been increased from 56rem to 64rem, giving more space for complex filter configurations.
- Smarter rule creation: When adding a new filter rule, the entity browser now opens automatically to help you quickly select properties.
- Improved predicate selector: We've replaced the browser’s default predicate selector with a styled dropdown for better consistency and usability.
- Retained values on predicate change: Changing the predicate no longer resets your selected value on the right-hand side, making editing faster and less frustrating.
- Better button placement: The Apply and Cancel buttons now appear at the bottom right of each filter rule, aligning with the left-to-right configuration flow.
- One rule editing at a time: You can now only edit one filter rule at a time. Opening another rule while one is being edited will cancel the unsaved changes of the previous rule—preventing conflicting updates.
- Clear error handling: If a referenced item in a filter is missing (e.g., due to deletion), both the filter option and the specific rule now show an appropriate error message (e.g., “Property not found”).
- Reference renames handled: When used references are renamed, those changes are now properly reflected after a refresh to all items. This wasn’t the case before.
- Password property: Password properties can no longer be selected on either side of a filter rule, since there's no valid use case for this.
- Enhanced "has-many" filtering: When filtering through a has-many relationship, the "includes" and "does not include" predicates appear. The accompanying token input on the right-hand side has been improved for both editing and reading states.
- ...and many other smaller UI/UX tweaks to streamline the filtering experience.
Improvements & fixes
Increased default Autocompletes take from 20 to 50
Value: We have updated the Autocomplete components (single and multi value) in order to increase the initial take when using the components at runtime. Previously, the initial take was 20 records by default. This has been changed to 50 by default in order to make these components more sufficient for multiple use-cases, since they don’t include any type of pagination.
Impact: This update will only be available in the latest version of the single- and multi Autocomplete components in the default Betty Block component set. Existing components already in use on pages will not automatically receive this update.
Up next
1. New filter user interface implementation
- Value: We’re introducing a new and improved filter interface throughout the Page builder, enhancing both the user experience and technical maintainability. Filters are used in three key areas — data components, page variables, and display logic. While primarily a technical refactoring, this release also includes a refreshed UI and improved UX for easier and more efficient filtering.
- Impact: Users will experience a new UI for filters, while the underlying metadata to the backend remains unchanged. There should also be zero impact at runtime because of this. We will be starting with switching to these new filters in data components, followed by page variables and display logic.
Timeframe:
-
- Data components filter option: Released
- Page variables filter: August 2025
- Display logic filter: August 2025
2. Toggle form changes syncing per action step
- Value: This feature will allow developers to enable or disable form change synchronization for individual action steps that include the 'value mapping' step option type, like the default Betty Blocks create and update steps.
Impact: This option enables the new time-saving synchronization feature to be applied to older forms. It allows you to synchronize form changes across multiple action steps simultaneously and provides the flexibility to disable the synchronization feature when it is not needed.
Timeframe: August 2025
3. Support for return to referring URL or deeplinking support
Value: In the Pages, we will be introducing deeplinking support when authenticating. After successfully authenticating (via username/password or custom authentication profiles), users will be automatically redirected to the original page they were trying to access. No more manual backtracking or copying URLs. The platform will remember where you came from and return you there post-login. This eliminates friction, saves time, and helps users stay in their flow.
Impact: This feature will only become available for applications running on the new pages compiler
Timeframe: August 2025
Models
Up next
Improving the current setup of Wasabi
- Value: We will be improving our current subaccounts and buckets setup of Wasabi Technologies to improve the performance of storing the assets. This change is part of our continuous efforts to optimize our services and ensure we leverage the most efficient and secure solutions available.
- Impact: No action is required nor expected from our users
Timeframe: Continuous releases till the end of August
Actions
Up next
Unlock high-code capabilities with the Wasm-based action builder
- Value:
- Unlocking high-code flexibility within low-code: By enabling high-coders to visually model Wasm components, Betty Blocks can bridge the gap between the perceived limitations of low-code and the flexibility of high-code. This enables developers who desire more control and customisation within a low-code environment.
- Breaking vendor lock-in: The ability to export Betty Blocks actions as Wasm components provides customers with the significant value of application portability. This means their actions are no longer tied solely to the Betty Blocks platform and can potentially be run elsewhere, increasing customer freedom and reducing concerns about vendor lock-in.
- Expanding code language support: The feature's potential to transform code written in various languages (Rust, Python, etc.) into Wasm opens up the Betty Blocks platform to a wider range of development skills and project types, breaking the limitations of proprietary low-code technologies.
- If you want to try out the Beta Wasm-based action builder, please reach out to lisanne@bettyblocks.com for the feature flag. What you will unlock with this feature flag:
- Create a Wasm action via the Actions IDE
- Feature: Choose the Wasm type when creating an action
- Value: Enable the new Action Builder that allows you to build Wasm components in a low-code environment
- Upload your custom Wasm components
- Feature: Expand your action builder with custom wasm components / functions, written in your preferred language.
- Value: High-code developers can build advanced, performance-critical components in any WebAssembly-supported language, such as Rust, Java, or Python. These components are brought into the platform as visual, reusable building blocks. Low-code developers can configure and orchestrate them using familiar drag-and-drop tooling, without writing a single line of code.
- Download your Wasm binary
- Feature: The ability to download the .wasm binary file and source code to inject this business logic into your high-code projects.
- Value: Add high-code logic to low-code apps with the upload, or extend high-code projects with low-code components.
- Create a Wasm action via the Actions IDE
Timeframe: Half of Q3 2025
My Betty Blocks
Up next
Sign-up flow for the AI-generated pages trial based on invite code
- Value: As a potential customer with an invite code, I can sign-up for the AI generated trial, so that I can try out this functionality within the platform.
- Impact: To be able to use this, you need to have an invite code.
Timeframe: Within 2 weeks.
Education
Up next:
New modular courses in the Academy- Feature: Continue creating a foundation for modular education by transitioning the existing learning paths into reusable modules
- Value: Provides better content organization and maintenance options, and more flexibility in terms of learning features at Betty Blocks
Platform roadmap
Want to know more about the upcoming features and functionalities of the Betty Blocks platform? Visit the platform roadmap of our community, where you can find most of the topics that we are currently working on and are planning to work on. Let us know your thoughts by upvoting the topics you believe are the most valuable!