Multipage apps contain pages to combine functionality and use cases. Standard Retool apps operate as single-page applications where all code and components is continually evaluated. Multipage apps are also supported by Retool Mobile where each screen functions as a separate page.

With multipage apps, Retool only evaluates the code and components of the page currently in view. The benefits of multipage apps include:

• Greater performance of large and complex apps. Since Retool only evaluates code and components for the current page, multipage apps are 30-40% faster than a single-page app.
• Seamless navigation between pages. Retool loads the complete app state whenever a user navigates to a single-page app. With multipage apps, navigation between pages is seamless and more responsive.
• Improved app management. Multipage apps can replace multiple apps in your organization, such as a team's frequently used apps. This reduces the number of apps to maintain and allows for easier permission management.
• Reduced module dependency. Modules are commonly used to create shared navigation menus across multiple single-page apps. With multipage apps, you can eliminate the need for additional modules and the complexities with maintaining them.

Each multipage app uses global and page scopes to separate pages. Globally scoped code, and Header and Sidebar frames, are available for use across every page, while each page has its own page-scoped code and components.

You can request access to the multipage app beta and explore the docs to learn more.

Retool is currently working on a new layout architecture, WidgetGrid, that significantly improves the performance of the canvas. Placement and arrangement of components, such as dragging to reposition, is up to 50% more responsive.

WidgetGrid is currently rolling out to cloud-hosted organizations as an opt-in beta and will be available in the next Edge release of self-hosted Retool. You can enable WidgetGrid from the status bar when viewing or editing an app. You can disable WidgetGrid at any time and provide feedback about any issues you experienced.

You can now connect your organizations to Sentry or Datadog for error monitoring. App errors will be reported with a callstack and descriptive tags when viewing and interacting with an app in preview or public (end-user) mode.

Subfolder organization of apps is now available as a public beta. You can create nested folders for more granular organization and permissions of Retool apps.

Organization admins can enable or disable subfolders in the Advanced settings section of the organization settings page.

Custom product pages allow organizations on the Business plan and above to replace Retool's login, reset password, signup, and invitation claims pages with custom Retool web apps.

This feature is currently an early access beta. Contact your account manager or reach out to request access.

Custom component libraries is the new approach to building custom React components for web apps. Previously, custom components were built directly within the App IDE. With custom component libraries, you can now build components locally in your development environment, then deploy to Retool. After deploying, you can drag and drop components into apps as you would any other component.

Custom components are contained within libraries, and each library has a unique name. Custom components deployed to Retool are automatically shown in the Component Library.

Custom Python libraries for Retool Workflows is now available as a public beta. You can add one of the built-in Python libraries or provide a custom list of libraries and versions.

A new and improved version of the Loop Block is now available in beta. If you'd like to participate, complete this form to request access.

The new Loop Block features:

• Iteration-level timeout of up to 30 seconds when executing the entire workflow.
• Parallel, sequential, and batched execution modes with iteration delays
• Improved iteration-level error handling to allow subsequent iterations to run.
• Iteration metadata that is accessible in subsequent blocks.

Once enabled, any new Loop blocks added to workflows will use Loop block v2. Existing Loop blocks will continue to function as before.

Internationalization (i18n) is now in beta for organizations on the Enterprise plan. This allows you to localize Retool app content and data.

This beta is available to cloud instances and self-hosted instances on version 3.38 or later. Contact your Retool account team to request early access.

A visually refreshed component library is currently available as an opt-in beta for cloud-hosted organizations. It contains minor style changes to many components, such as:

• An updated color palette.
• Changes to the active and hover state appearance for buttons and inputs.
• Removing borders on input attachments and buttons.
• Fixing inconsistencies with component spacing, font weight, border radius, etc.
• A new look for the Tab and Navigation components.

Any style overrides you've made will still be retained.

Click Get started and leave a comment to request access.