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
Page last updated with information in Pages overview
Value: In the Pages overview we have introduced a new “last updated” column, showing when each page was last modified with sorting capability.
Impact: You will be able to easily find the most recently edited pages, saving you time.
Updated page settings
Value: Page settings interface (as well as some functionality) has been updated to improve consistency and usability across the platform. Page settings are now accessible via a right-hand side panel, just like Action settings. Clicking the settings button in the top navigation will open this panel, streamlining how you navigate and edit page-level configurations.
- Updated look and feel - The visual design of the page settings elements now aligns with the rest of the Page builder interface, ensuring a more cohesive and intuitive user experience.
- Inline validation errors - Validation errors (e.g. when a page path is already in use) now appear within the relevant form field. Clear, contextual error messages make it easier to understand and resolve issues.
- Changed path field behavior - When setting the path, for example, your home page with root path “/”, the field can now be left blank. While each page path still needs to be unique, the field is no longer required as before and you no longer need to manually include the leading slash “/” for every page path.
- Custom component set URL validation - When specifying a custom component set in the Page settings, a new frontend validation checks whether the entered value is a valid URL. This helps prevent configuration errors early on.
- Updated component control bar
Value: The Component control bar interface has also been updated for easier identification and accurate component color coding to make the control bar more visually informative. - Component icon display - The control bar now shows the icon of the component, making it easier to identify at a glance.
- Accurate color coding - The control bar now correctly reflects the color associated with the selected item—whether it’s a component, widget, partial, or another type—ensuring better visual clarity and consistency.
- Overflow fix - We’ve resolved an issue where the component control bar buttons (e.g., Delete, Duplicate) could overflow off-screen. This fix ensures that the control bar remains fully visible and clickable, no matter where your component is placed.
Improvements & fixes
Fix: Scrolling issue in the component options sidebar
Value: We’ve resolved a bug where the component option sidebar’s footer buttons were overlapping with content, preventing users from scrolling to the bottom. This issue has been fixed now. You can now scroll through the entire component options sidebar without any obstruction.
Impact: Users do not need to take any additional steps to benefit from this.
Fix: Unintended display of partial list in sidebar
Value: We’ve resolved an issue where the partials list would incorrectly remain visible in the sidebar after opening a partial in edit mode from the partials list view. This behavior has been corrected. Now, when opening a partial in edit mode, the sidebar will default to the Widgets tab. If the Components tab was previously selected, it will remain active during partial editing as expected.
Impact: Users do not need to take any additional steps to benefit from this.
Up next
Launch of new pages compiler - for 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: June/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 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: June/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 a “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: Q2 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: Q2 2025
Actions
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
Master template deviation (Beta)
Value: As a Master Template developer, it is now possible to create a branch under a sub-application of the master template, so that deviations can be made in that application to cater to app-specific use-cases.
Impact: 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.
Improvements & fixes
Fix: Sidebar overlapping content on small screens
Value: Prevent the sidebar from overlapping content on small screens
Impact: Company overview and selecting an application template in the create flow
Fix: Stuck on redirection when linking to items from the merge overview
Value: Prevent dead links in the building environment when navigating from the merge overview.
Impact: Clicking on links for changes of partials, public files and authentication profiles.
Fix: Uploading large images
Value: Large images no longer get stuck on upload or resulting in errors.
Impact: Uploading organization, application, template or gallery images.
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
Improvements & fixes
Updated the articles to reflect the latest UI and functionality enhancements:
Up next
Create new assignments and quizzes for the Advanced path.
Timeframe: within 2 weeks
Later this year:
- New modular courses in 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!