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
Link to page with page variable property mapping
Value: The page component option type has been enhanced to give you more flexibility when passing data between pages. Previously, you could only map properties from model data exposed by data components on the page. Now, you can also leverage page variable properties and page input variables without needing to nest the component inside a data component.
For example, imagine a page that fetches a Project record using an object page variable. On this page, you might have an “Edit project” button that opens the edit page. With this enhancement, you can directly pass the ID property of the Project object page variable as input to the edit page, ensuring it receives the required ID seamlessly.
This makes them easier to recognize and avoids confusion with other variables.
Impact: This feature is available for page builder applications running on the new Pages compiler only.
Up next
1. Link to page with page variable property mapping when using Redirect interaction
Value: We will upgrade the Redirect interaction function to give you more flexibility when passing data between pages. Currently, you can only map properties from model data exposed by data components on the page. Now, you can also leverage page variable properties and page input variables without needing to nest the component inside a data component
Impact: This feature is available for page builder applications running on the new Pages compiler only
Timeframe: October 2025
2. Page layouts
Value: We are introducing new page layouts in Pages, a feature that explicitly separates the Layout and Body sections of a page, the two fundamental building blocks of any application page.
With page layouts, you can define multiple reusable layouts (for example, with different headers, navigation, or footers) and assign a single layout to each page. This brings significant benefits:
- Reusability – build once, apply across multiple pages
- Consistency – ensure a uniform look and feel throughout the application
- Scalability – manage and evolve layouts independently from page content
Impact: This feature will only be compatible with applications running on the new Pages compiler
Timeframe: October 2025
Actions
New feature
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
-
- 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
- Upload your custom Wasm components
- Add input and action variables
- Download your Wasm binary
Want to read more about the Wasm-based action builder? Click here
Improvements & fixes
Improvement: Removed the switch to old logs
- Value: With the release of the new log page a couple of months ago, the user was able to visit the old logs via a button Switch to old logs. Since the old logs were not present anymore, we have removed the button from the Logs page.
- Impact: No action required from users.
Fix: Download button in the Wasm-based action builder
- Value: Previously, when you redirected from the action builder to page builder and came back, the download button of your wasm action was not active anymore. The user needed to trigger the compiler again in order to download the ZIP file.
- Impact: No action required from users.
Up next
1. Running wasm actions from the IDE
- Value: Builders can now run Wasm actions directly from the Wasm Actions IDE, without needing to download and execute them externally. This brings the same smooth testing experience that was previously available in the NextGen Actions IDE, allowing for faster iteration and more efficient debugging.
- Impact: Once the feature flag is enabled, builders can create Wasm-type actions and use the new “Test run” functionality directly within the IDE. No additional setup or external tools are required.
- Timeframe: Within two weeks
2. Multifunctions in a custom wasm component
- Value: Builders can upload multiple functions from a single wasm file in one step, instead of uploading each function individually. This significantly improves the developer experience by reducing repetitive work, lowering the risk of errors, and making it easier to bring complete use cases, such as full API integrations, into projects. Additionally, it enables reusable patterns by allowing builders to package and share multifunction Wasm components via the Block Store.
- Impact: With this update, builders can efficiently import an entire set of related functions (e.g., create, read, update, delete, authentication) from one wasm file, streamlining the setup of complex integrations. No extra steps are required beyond uploading the wasm file containing multiple functions.
- Timeframe: Upcoming quarter
3. Wasm components in the Block Store
- Value: Builders gain access to pre-built Wasm components directly from the Block Store, allowing them to quickly discover and leverage existing functionality in their apps. This reduces the need to manually recreate common functionality, accelerates development, and unlocks more reusable and scalable solutions.
- Impact: Once available, builders will be able to browse and install Wasm components from the Block Store just like any other block. This visibility makes it easier to integrate complex functionality without starting from scratch.
- Timeframe: Upcoming quarter
My Betty Blocks
Improvements & fixes
1. Allow all email domains on trial signup
- Value: As a prospective customer evaluating our product, I want to use my personal email,
Impact: During the sign-up of the trial: https://www.bettyblocks.com/ai-page-gen-trial.
2. 'Created at' column in applications overview
- Value: As a company admin, I want to see the 'created at' of all applications, so that I can govern the development efforts
- Impact: When navigating to the applications table in the company overview a new column has been added showing the created date.
3. Company overview navigation
- Value: Selecting the company overview when it's already selected no longer results in a blank screen.
- Impact: When selecting the company overview in the sidebar twice.
4. Change block name and logo
- Value: As a block owner, I want to manage the name and logo of my block so that I can create consistency in naming and make them easier to find.
- Impact: When editing a block in the Block Store we have added a title and icon upload input.
5. Remove dead links in deleted items
- Value: As a user with merge permissions, I don’t want to be distracted by dead links in my merge changes overview, to improve the UX.
- Impact: When opening the merge plan and having deleted item changes, they are no longer clickable links.
6. Update conflict tooltip for deleted item used.
- Value: As a user with merge permissions, I want to have clear tooltips, so that I’m guided in using more complex functionality.
- Impact: When opening the merge plan and having deleted item conflicts, the tooltip now no longer indicates these items can be removed when they are already removed.
Up next
Trial signup via social single sign-on
Value: As a prospective customer evaluating our product, I want to sign up for a trial using my existing SSO provider (e.g., Google, Microsoft, GitHub) so that I can quickly and securely start using the product without creating and remembering new credentials.
Impact: During the sign-up of the trial (https://www.bettyblocks.com/ai-page-gen-trial) select one of social items instead of username and password.
Timeframe: Upcoming 2 weeks.
Education
New
1. Handling and preventing action errors- Value: This guide helps builders create more reliable actions by preventing, handling, and troubleshooting errors.
- Impact: Applications run more smoothly with fewer disruptions, improving both user and builder experience.
- Value: This lesson teaches builders how to display model data on a page using a Data table component
- Impact:Builders can present information clearly to end-users, making applications more informative and useful.
Up next
1. SSO configuration documents: Guidance on available SSO setups, required information, and a new article on implementing Azure SSO via SAML with current SAML functions/action steps.
Timeframe: Upcoming two weeks
2. Building with data: Academy course on using data to build your pages
Timeframe: Upcoming two weeks
3. Debugging and using Logs: Academy course on monitoring, testing, and debugging business logic with Logs, Log messages, and GraphQL playground.
Timeframe: Mid-October
4. Branching documents: Refining Branching reference and creating a new Branching best practices documents
Timeframe: Beginning of October
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!