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
Launch of the new compiler
- Value: We’ve launched a powerful upgrade to our platform—the 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, rather than querying all properties.
- Faster performance when compiling pages from a merge.
- Impact: This feature has been rolled out to a pre-selected customer’s private zone first. At this time, we can’t commit to a specific timeline for launching it to all zones and all existing applications yet.
Improvements & fixes
1. Reduced IDE downtime during releases
- Value: We've optimized the release process for the platform’s IDE, cutting potential downtime to just one second if you're refreshing your browser during a deployment. Previously, this interruption could last up to 30 seconds or more.
- Impact: No action required from users.
2. Strengthened page compile validation for authentication profiles
- Value: We've improved the page compile validation step to detect missing login redirect pages in authentication profiles. Previously, this check was only applied if a redirect page had never been set (after creation of the authentication profile). Now, it also covers cases where the previously selected login page has been deleted. This ensures authentication profiles cannot be compiled with broken or invalid redirect references to prevent unexpected behavior at runtime.
- Impact: Please verify that all your authentication profiles include a valid login redirect page. Beyond this, no further action is required—this safeguard is now in place to help prevent runtime errors.
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: July 2025
- Page variables filter: July 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 '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. 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: August 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
Fixes
- Debugging logs with conditionals now have the correct order
- Updating action step name via the save button
- When an action step is crashing, the log error will be shown on the step
- Duplicated output variable of the loop step
- Press Enter behaviour in edit filter rules of the action builder
- Long variable names are not truncated in the logs IDE
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: Beginning of Q3 2025
My Betty Blocks
Improvements & fixes
Show application is disabled
- Value: As an application manager it is more clear to me that my application is disabled, so that I can contact Betty Blocks support.
- Impact: On the application detail view there is a new label displayed and all menu items are disabled where needed.
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. Sign-up flow for 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
New
Creating a custom page component (with TypeScript)
- Value: This article helps low-code developers create and reuse their own components within the page builder
- Impact: It enables more flexible design, faster development workflows, and consistent use of custom elements across projects
Improvements & fixes
- Setting up your low-code environment. Updated flow explained
Up next
1. 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!