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
Text & Title component color inherits a theme by default
Value: We've updated the default behavior of the Text and Title components. Newly added instances will now inherit their text color from the surrounding text style in the theme by default, ensuring more consistent styling across your design. When you update the text style color in the theme settings, all Text and Title components using theme color inheritance will automatically reflect the change. If needed, you can still override the text color by selecting a different general theme color manually.
Impact: This update only applies to newly added components. Existing components on the page prior to this release will remain unchanged and will not have the ability to inherit the color from the theme.
Open internal page in a new tab at Menu item components
Value: We've added a new option in the Menu item components to open the navigation to an internal page in a new browser tab, ensuring consistency when using external navigation.
Impact: This update only applies to newly added components. Existing components on the page prior to this release will remain unchanged and will not have this new ability.
Improved submenu customization in Menu component
Value: The default Menu component in our standard component set has been upgraded to offer greater submenu customization. You can now drag and drop components of type ‘body’ or ‘container’ directly into the component, giving you much more design flexibility for submenus. This enables advanced use cases such as:
- Multi-column submenu
- Deeply nested submenus
- Notification centers within a menu
- Fully customizable, layout-rich menus
Impact: This update only applies to newly added components. Existing components on the page prior to this release will remain unchanged and will not have this new ability.
Improved configuration modal for Update form component
Value: We've updated the configuration modal that appears when adding an Update form component to a page. You can now insert the component without configuring a data context upfront. This streamlines workflows where input setups are already handled elsewhere on the page, making it easier to reuse Update forms in more flexible situations.
Impact: When adding an Update form component to the page, the configuration modal consists of the options in the button group. When choosing ‘other’, the form is added without data context.
Improvements & fixes
Fix: Several component tree fixes
Value: Since the release of the new component tree we have received feedback from users. Over the last two weeks, we’ve resolved much of the feedback. Here is a summary list of the resolved issues:
- Tooltips in the tree no longer disappear after minimizing and then maximizing the panel.
- The 3-dot (more options) button now correctly appears for locked widgets in the tree.
- Renaming a deeply nested component from the tree now uses a properly sized text input field.
- Drag actions are no longer allowed between a widget and its dropzone(s) component in the tree.
- Toggling the dropzone checkbox on a component no longer causes expand/collapse buttons for its child components to disappear in the tree.
- Renaming a component from the tree immediately after renaming it from the sidebar now correctly displays the updated name.
Impact: Users do not need to take any additional steps to benefit from these fixes.
Fix: Page settings skeleton loader
Value: We’ve resolved a UI bug where the Page settings skeleton loader at the SEO description field was too large in height compared to the other fields. This issue has been fixed now.
Impact: Users do not need to take any additional steps to benefit from this.
Fix: Page settings button in Partial editor
Value: We’ve resolved a UI bug where the Page settings button was shown when a user had opened a partial in edit mode. At the moment, there is no support for Partial settings yet.
Impact: Users do not need to take any additional steps to benefit from this.
Up next
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. Here are three benefits of using the new pages compiler:
- When clicking ‘Play’ the new compiler compiles all pages changed instead of just one.
- It generates queries based on what the page requires instead of querying all properties.
- Faster performance when compiling pages from a merge.
Impact: This feature will first be rolled out to newly created applications, whether started from scratch or from a template. Existing applications will transition to the new pages compiler in a later phase.
Timeframe: July 2025
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.
Timeframe: July/August 2025 - in new applications (the further roll-out is dependent on the new compiler roll-out)
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.
- Fixes for approximately 10 known issues.
- This upgrade lays the groundwork for more flexible and maintainable filter features in the future.
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: July 2025
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
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
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
Actions IDE technology update
Value: We've updated the underlying packages of the Actions IDE to align with internal quality standards.
Impact: As a result, you may notice a few temporary UI issues:
- The back button is currently missing when navigating from another page.
- The development banner may push lower buttons off the page.
These issues are known and will be resolved in upcoming updates.
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.
Timeframe: Beginning of Q3 2025
My Betty Blocks
New features
Rollback on sub-application for master templates (Beta)
Value: Master Template developers are able to perform rollbacks on sub-applications to restore their application to a working state.
Impact: The Master Template functionality is in beta and behind a feature flag. If you are interested in trying out this functionality, get in touch with support or your Betty Blocks contact person.
Auto Betty Blocks support removal
Value: Betty Blocks employees are automatically removed from applications after offering support to customers, for compliance with access and agreements with the customer.
Improvements & fixes
Improvement: Audit log adds more context on deletions
Value: Company admins are able to view what was deleted in the context, so that they know what was actually deleted. Next to that, we enhanced the context for sandboxes/branches so that it is clear for what application this is.
Impact: The audit logs when removing users from different organizations, applications, sandboxes, etc.
Fix: Company dashboard data not loading due to big data
Value: Prevent the updating of company dashboard data in certain cases, disturbing graphs.
Impact: Company dashboard.
Up next
Resolve the 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.
Timeframe: Within 2 weeks
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.
Timeframe: Within 4 weeks
Copy test data from the 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 8 weeks
Education
New
Advanced path - Betty Blocks Academy: Added new assignments and quizzes to support deeper learning
Improvements & fixes
- Media component: Included guidance on resolving video display issues
- Creating component interactions: Added a new use case demonstrating how to use the Refetch page variable interaction
Up next
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
Updated Essential Path – Betty Blocks Academy
Value: New videos reflect the current building flow on the platform
Impact: Improves the learning experience for new users and shortens onboarding time
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!