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
Improvements & fixes
1. Button accessibility update
- Value: We have enhanced the Button component to make it compatible with the latest accessibility standards. Buttons that for example launch or close modal popups do now respond to keyboard interactions, ensuring a more inclusive and user-friendly experience for all user
- Impact: This update will only be available in the latest version of the button component in the default Betty Block component set. Existing components already in use on pages will not automatically receive this update.
Up next
1. Launch of new Pages compiler - to new applications first
- Value: We’re preparing to launch a powerful upgrade to our platform—a new Pages compiler. In recent release notes, we have communicated to launch this to all new applications over all zones. This plan has changed, and we will start launching smaller with only one Customer’s private cluster.
Customer’s private cluster: July 2025
The rest of the zones: At this time, we cannot commit to a specific timeline for their implementation yet
2. Accessing logged-in user data via variables on pages
- Value: We will enhance usability when working with logged-in user data on pages by automatically providing authentication profile variables (representing logged-in users) across Pages. This is what you are able to do with authentication profile variables: using them inside component options on a page, within filters of data components and other page variables on a page, inside partials on a page, and the use of current user role(s) in conditional display logic filtering on a page for easier configuration of show and hide logic based on the user’s role(s).
- Impact: Users will no longer need to manually add data containers to make logged-in user information available across pages, simplifying workflows and improving efficiency without additional setup. This feature will only be available for applications running on the new compiler. This will not be compatible with the current compiler.
Customer’s private cluster: July 2025
The rest of the zones: At this time, we cannot commit to a specific timeline for their implementation yet
3. 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: July 2025
- Page variables filter: July 2025
- Display logic filter: August 2025
4. 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 '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: July 2025
5. Color component option overhaul
- Value: Users will be able to choose colors more visually through a color picker instead of a textual dropdown, including the ability to select custom colors beyond your application theme values.
- Impact: Users gain clearer visual indicators and greater flexibility when styling components, resulting in smoother, more enjoyable, and more precise customization of their applications.
Timeframe: July 2025
6. Spacing option added flexibility
- Value: In addition to the default spacing options (S, M, L, XL), users will have the ability to define custom spacing values to better suit their layout needs.
- Impact: Users gain more spacing flexibility and it empowers more precise and personalized design control.
Timeframe: July 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
Improvements & fixes
Able to select a rich text property in a "Text" or "Value" option of an action function
- Value: With this improvement, you're now able to select both Rich text and Multi-line text properties (and even more). Most important use case: you can now select an email template from a rich text or multi-line text property in the Liquid step, allowing you to build a more dynamic email template setup in your next gen applications with default action steps from the block store. Next to that, you are now also able to select a datetime property directly in the first option of the function “Date time offset”, so you don’t have to use an Expression step to convert the value anymore.
- Impact: No action is required nor expected from our users.
Up next
Unlock high-code capabilities with the WasmBuilder
- 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.
- Impact: Transform code written in various languages into Wasm, which enables greater flexibility and more control over the application. If you want to try out the Beta Wasm Builder, please reach out to lisanne@bettyblocks.com for the feature flag.
Timeframe: Beginning of Q3 2025
My Betty Blocks
New features
1. Resolve already modified merge conflict
- Value: As a user with merge change permissions, I’m able to choose the incoming or current changes in the merge overview, so that I can merge the desired changes to my application.
- Impact: This functionality is available for our branching and master template functionality. These are both behind a feature flag to be able to be adopted.
2. Allow builders to resume failed merges
- Value: Enable builders to resume failed merges without having to contact Betty Blocks support to speed up the merge process.
- Impact: Builders will be able to retry the merge from the merge overview.
3. Build activity on company applications table
- Value: Allow company managers to govern the building activity per application, so that they can monitor the applications that are being actively developed.
- Impact: Company managers with the permissions to view the company overview can see a new column in the applications table.
Improvements & fixes
1. View changes of updated style
- Value: Viewing the detailed changes of an updated style in the merge overview no longer results in an error.
- Impact: View the merge overview when there is an update to a style in the application, select the view changes button.
2. Sandbox & branch creation progress bar
- Value: The progress bar of the sandbox and branch is now displayed instantly again, so that it's clear what the creation progress is.
- Impact: Create a sandbox or branch and watch the progress bar.
Up next
1. View page and action structure conflicts
- Value: As a developer using branching functionality I’m able to view when there is a conflicting update on the structure of a page or action, so that I know I need to manually resolve this to be able to release it.
- Impact: When having two branches that both edit the same page or action structure this conflict will be visible in the merge overview. This functionality is available for our branching and master template functionality. These are both behind a feature flag to be able to be adopted.
Timeframe: Within 2 weeks.
2. Copy test data from a sandbox
- Value: As a user with copy test data permission it's possible to copy the test data of a sandbox to improve the speed of getting started with development.
- Impact: When creating a new sandbox or branch, the user has the option to copy data with a limitation of 1000 records.
Timeframe: Within 4 weeks.
Education
New
- Value: The updated videos now accurately demonstrate the current building process on the platform. The Essential path covers a broader range of building with widgets and highlights the use of page variables for faster development
- Impact: This enhancement delivers a smoother onboarding experience for new users, accelerates learning, and introduces more intuitive building options such as template-based workflows.
Improvements & fixes
- Create secure reset password function: Updated, more secure flow explained
- Understanding value of Next-Gen Actions: Explore differences between the Next-gen and Classic Actions
Up next
1. Creating custom components with TypeScript
- Value: Enables developers to build custom components using modern TypeScript standards, aligned with the CLI’s prefab boilerplate
- Impact: Removes the reliance on outdated JavaScript-based materials and reduces fallback to classic actions, unlocking the full potential of custom component development
Timeframe: upcoming 2 weeks
2. What is Wasm builder?
- Value: Wasm Builder lets you visually create Wasm components in Betty Blocks, use multiple programming languages, and export your logic for use wherever you need it.
- Impact: You can build more flexible, portable solutions, reduce vendor lock-in, and meet advanced project requirements without leaving the low-code environment.
Timeframe: upcoming 2 weeks
Later this year:
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!