Docs
BlogChangelogStar Us on GitHub
HomeGuidesEASReferenceLearn
ArchiveExpo SnackDiscord and ForumsNewsletter

Release statuses

Edit page

Learn about alpha, beta, and stable release statuses and how they affect feature stability when using Expo SDK and Expo Application Services (EAS).

Expo uses different 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.

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 major version bumps
  • Implementation may change substantially based on feedback
  • May have known bugs or performance issues
  • 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.

Beta

Beta features are feature-complete and undergoing final validation. These features have core functionality implemented and are being prepared for stable release.

What to expect:

  • Core functionality is complete and API shape is mostly settled
  • May have minor bugs or edge cases that are being addressed
  • 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 any status badge are considered stable and are fully released for production use. These features have been thoroughly tested and follow semantic versioning for any future changes.

What to expect:

  • Production-ready with full support
  • Breaking changes only occur in major version releases
  • Performance and stability have been validated
  • Documentation and examples available

Stable features are ready for use in any application. You can rely on them following semantic versioning principles, meaning breaking changes will only occur in major version updates.

Deprecated

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

What to expect:

  • Warnings in documentation and code when using deprecated features
  • No new features or improvements will be made
  • Removal in future major releases

When you encounter a deprecated feature, we recommend planning to migrate to the suggested alternatives as soon as possible to ensure your projects remain up-to-date and maintainable.