Previews are the easiest way to test your app – all you need is a preview link and you’re good to go. You can run previews either directly from your device, using the tuist run command or the Tuist macOS app.
However, after teams starting to use our previews in the wild, we’ve realized the current implementation had two issues:
- Previews were not grouped
- When running a preview, we were downloading all platforms instead of just the one requested
The latest CLI, macOS app, and server remedy both of these issues. We recommend that you update both the CLI and the macOS app to their latest versions to start benefiting from these improvements.
Grouped builds
When running tuist share, we automatically group the build into a common preview based on the:
- bundle identifier
- commit SHA
- app version
- app name
That means when you run tuist share from multiple jobs as part of the same workflow, you will now end up with a single preview link for all platforms that you shared.
Before, each tuist share invocation would create a separate preview, and when sharing the preview with your colleagues, you would need to share all of those, so that everybody has access to all supported platforms.
Optimized downloads
When you shared multiple platforms as part of tuist share, they would get stored as a single archive. When running such preview, we would download that single archive, unarchive it, and then run the selected platform. This resulted in suboptimal downloads as we were downloading more than necessary. Instead, each platform/destination is now uploaded separately and we only download the bundle for the requested platform.
In other words, running the preview should be much faster now 
What’s next
What’s next for previews? @pepicrft outlined our vision for Tuist Previews on our blog: The Future of App Development: Tuist Previews in an AI-Powered World. Additionally, we are now getting back to the iOS app to make running previews from your device even easier.