as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
Ring
AWS
Documentation
Support
Contact Us
My Cases
Ring

Publish Your Ring Application

After your app passes certification, the Publish phase lets you control how it reaches Ring users. You can roll out gradually, to a closed beta group, or to everyone at once.

Prerequisites

  • At least one app version has passed certification (status: "Certified version available for rollout")
  • Your production endpoints are stable and ready for traffic

Accessing the Rollout Process

From your app's overview page, click the Publish section (step 5 in the app lifecycle). This opens the Rollout process page.

If a certified version is available, you'll see a banner confirming it along with an Initiate rollout process button. You also have access to:

  • Review Version History — a log of all app versions, their statuses (e.g., Certification Under Review, Deployment Pending, Certification Withdrawn), and last-active timestamps.

Initiating a Rollout

Click Initiate rollout process. The rollout plan screen presents three configuration steps:

1. Distribution Location

This controls the geographic availability of your app — which Ring users can discover and install it.

Click the Distribution location card to open the location picker. You have two options:

  • United States (Nationwide) — available to all Ring users across the US.
  • Specific US States — restrict availability to selected states only. A checklist lets you pick individual states or use "Select all."

Distribution is currently limited to the US. International locations are not yet supported.

Choose your target region and click Save.

2. App Version

The certified version is pre-selected (e.g., v1 (Certified 02/06/2026)). Verify this is the version you intend to release.

3. Rollout Strategy

Pick one of three strategies:

Strategy Description Use case
Gradual rollout Deploy to a percentage of users, then increase over time up to 100%. Minimize risk on new launches or major updates.
Beta rollout Deploy to a closed group of beta testers via an invite link. Validate with real users before a wider release.
Full rollout Deploy to 100% of users immediately. When you're confident the app is production-ready.

Once everything looks right, click Confirm.


Rollout Strategy Details

Gradual Rollout

After confirming a gradual rollout, the portal shows a progress bar with your current rollout percentage (starts at 0%).

You control the pace with two actions:

  • Increase to 10% — bump traffic to the next increment.
  • Increase to 100% — skip straight to full availability.

A Roll back button is always available to revert the deployment.

Increase the percentage in stages as you gain confidence from monitoring. When you're ready, push to 100% to complete the rollout.

Beta Rollout

After confirming a beta rollout, the portal generates a Beta Enrollment URL.

Share this URL with the Ring users you want as testers. When they visit the link, they confirm participation in your beta program — no need to collect email addresses on your end.

Key details:

  • Maximum of 10 beta users per app.
  • A Rollback button lets you revert the beta deployment at any time.

When beta testing is complete and you're satisfied with the results, you can proceed to a wider rollout (gradual or full) by initiating a new rollout for the same version.

Full Rollout

Selecting full rollout triggers a confirmation dialog warning that the app will become available to all Ring customers on the Appstore.

Review the warning, then click Rollout to production to proceed, or Cancel to go back.

Once confirmed, the app deploys to 100% of users in your selected distribution location immediately.


After Rollout

When your app is live, the Rollout process page shows a success banner confirming the version is in production.

A Live configuration section displays your app's details:

  • App name
  • App type
  • OAuth client ID
  • Access token URL

From here you can:

  • Click View in Appstore to see your published listing.
  • Update the Distribution location at any time.
  • Access Review Version History to track all versions.

Rolling Back

During any active rollout (gradual, beta, or full), a Roll back button is available on the Rollout process page. Use it if you discover issues post-deployment. The rollback reverts your app to its previous state.

Once a rollout is fully complete and you need to make changes, submit a new app version through the certification process.


Version History

Click Review Version History from the Rollout process page to see a table of all app versions with:

  • Version number (v1, v2, v3, …)
  • Status (e.g., Deployment Pending, Certification Under Review, Certification Withdrawn)
  • Last active date

The summary at the top shows total versions, the current live version, and the latest version number.