This documentation is available as Markdown for AI agents and LLMs. See the full Markdown index or append .md to any documentation URL.

Learn about the experimental, alpha, preview, beta, stable, and deprecated release statuses used across the Expo SDK, Expo Router, EAS, and Expo CLI.

Expo uses various release statuses to indicate the stability and readiness of its tools and services. Understanding these statuses can help you make informed decisions about which features and versions to use in your projects.

These statuses are not a single pipeline that every feature moves through. Each product area uses the statuses that fit how it ships:

Note: Any feature can become deprecated at the end of its life, and individual APIs inside otherwise stable libraries can be experimental.

Experimental

Experimental features are early explorations of new ideas. They are shared to validate a direction and we are still deciding whether the feature should exist at all.

What to expect:

• May change significantly or be removed entirely in any release
• APIs are subject to change without notice or deprecation warnings
• Treat the implementation of an experimental feature as a proof of concept rather than final
• May have known bugs, missing functionality, or performance issues, and fixes are not guaranteed
• Not recommended for production apps

Experimental features are the earliest opportunity to try new ideas and influence whether they move forward. Test them in development environments and share your feedback to help us decide what happens next.

Note: This Experimental status is different from the experiments field in the app config. That field enables opt-in features, which are not necessarily experimental in your Expo project's app config. For example, experiments.typedRoutes enables typed routes, which is a beta feature.

Alpha

Alpha features are available for early testing but may have significant limitations. These features are in the earliest stage of development and are shared with the community to gather feedback and shape their direction.

What to expect:

• APIs are subject to breaking changes without a new SDK release
• Implementation may change substantially based on feedback
• Not recommended for production apps

Alpha features are opportunities to influence the future of Expo. We encourage you to test these features in development environments and provide feedback to help us refine them before they reach a wider audience.

Preview

Preview features provide an early look at a focused slice of new functionality. They are designed with minimal overhead and limited scope, but they are not yet feature-complete. You'll mostly see this status on new EAS services.

What to expect:

• A focused slice of functionality, not the full feature set
• APIs are subject to breaking changes as the feature is built out
• Can be used in production with thorough testing

The purpose of a preview is to share new functionality early and gather feedback about a specific slice before building it out further. Your input directly helps shape the direction of the feature. Share your feedback to help us prioritize what to build next.

Beta

Beta features are feature-complete and undergoing final validation before a stable release. You'll mostly see this status on EAS services and on SDK libraries that are close to stable.

What to expect:

• Core functionality is complete
• Breaking changes are possible but unlikely unless critical issues are found
• Can be used in production with thorough testing

Beta features are ready for real-world testing. While we don't expect major changes, we recommend testing thoroughly if you plan to use them in production. Your feedback during this stage helps us catch any remaining issues before the stable release.

Stable

Features without a status badge are stable and fully released for production use.

What to expect:

• Production-ready with full support
• Per semantic versioning, breaking changes to stable features only occur in new major versions

Deprecated

Deprecated features are no longer recommended for use and will be removed in a future release. We provide deprecation warnings to give developers time to transition away from these features.

What to expect:

• Documentation and code show deprecation warnings
• Expo may not accept feedback or issues for deprecated APIs
• Removal of deprecated features and APIs happens in a new SDK release