Filtering is now supported in the Console and State tabs of the Debug Tools.

Users can filter logs and states using any free text, negation, regex, or exact phrases:

• Free text: Matches any string.
• Negation: Prefix with - to exclude a match. For example: -error
• Regex: Use slashes for regex. For example: /^foo/
• Exact phrases: Wrap multi-word strings in quotes. For example: "query failed"

You can combine filters using spaces (e.g. "query failed" -/error/ success).

The Offline Assets app setting and PDF Viewer component are now generally available on Retool Mobile. You can use the PDF Viewer to upload and view files from URL, Retool Storage, Offline Asset, or JavaScript.

Using the Offline Asset PDF source allows you to store PDF files that can be retrieved and viewed offline, or in situations where internet connectivity is limited.

An improved version of the File Input component for Mobile is currently available on Retool Cloud and on Self-hosted Retool 3.168.0 or later.

This includes:

• Multi-file support – Users can now upload multiple files at once instead of being limited to a single file.
• Blob URL exposure – The component now exposes blob URLs to the value property in the component state.

An improved version of the Scanner component for Retool Mobile is currently in private beta on Retool Cloud and on Self-hosted Retool 3.173.0 or later.

This includes:

• The ability to restrict or select from multiple barcode symbologies to scan.
• The ability to select between Manual or Automatic scan modes.
• While scanning from the native app, there is a visual indication of what is being scanned (a bounding box) when hovering over a barcode, as well as a checkmark when a scan is successful.
• Scanner V2 does not have the autoClose property.

Previously, Retool Mobile only offered a component-based NFC reader, and we now support a resource-based NFC functionality that can both read and write.

The legacy option to create single-page apps has now been deprecated and is no longer available. Going forward, all newly created Retool apps support multiple pages, and newly created mobile apps support multiple screens.

Your existing single-page apps will continue to function as expected, and you are not required to migrate them. If you would like to do so, you can import legacy single-page apps as pages or use the Duplicate to multipage action on the apps landing 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.
• Simplified code sharing. The mechanisms for sharing code and components in multipage apps (global code, frames) are lower friction, easier to set up, and more powerful than the mechanisms for sharing code across apps (modules, query library).

You can set up integrations with Datadog and Sentry. With these integrations, app errors are reported with a callstack and descriptive tags when you view and interact with an app in preview or public (end-user) mode.

To connect third-party observability providers, you can report app errors using Retool Events and build a workflow that triggers whenever an app error occurs and automatically notifies your observability provider.

The Microphone component for Retool Mobile can record audio using the built-in microphone. Recordings are Base64-encoded in WebM format, and audio playback displays a progress bar and elapsed time.

The Slider component for Retool Mobile enables users to select a number value with a UI slider.

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.