Publish Your Ring Application
Ring App Store - Publish Phase
This document covers the publishing and rollout process for Ring App Store applications through the Amazon Developer Portal.
Table of Contents
Overview
The Publish phase is the final stage in the Ring App Store lifecycle (Configure → Develop → Certify → Publish). After your app configuration has passed certification, you can initiate a rollout to make your app available to Ring users.
What is a Rollout?
A rollout is the controlled deployment of your certified app configuration to Ring users. The rollout process allows you to:
- Control deployment: Choose how your app reaches users
- Test with beta users: Deploy to specific users for testing and feedback
- Track milestones: Monitor rollout progress
- Pause if needed: Stop deployment if issues are discovered
- Rollback capability: Revert to previous version during rollout process
Rollout Control
Important: You maintain full control during the rollout process and can rollback if necessary. This ensures you can respond quickly to any issues discovered after deployment begins.
Prerequisites
Before initiating a rollout, ensure you have completed:
- Certification Phase Completed
- App configuration has passed Ring Team review
- Status shows "Certified version available for rollout"
- Certification date is displayed (e.g., "Certified 02/06/2026")
- Production Endpoints Ready
- All configured endpoints are stable and production-ready
- Endpoints can handle expected user traffic
- Monitoring and logging are in place
- Error handling is robust
- Support Infrastructure
- Customer support processes established
- Documentation for end users available
- Team ready to respond to user feedback
- Incident response plan in place
- Testing Completed
- End-to-end testing completed successfully
- Beta testing (if applicable) completed with positive results
- Performance testing under expected load
- Edge cases and error scenarios validated
Rollout Process
Step 1: Access Rollout Process
Click manage on the app record on the Apps Portal.
The app details screen appears with its five sections: Configure, Build, Test, Certify and Publish
Click on the Publish section.
Page Description: "Manage how your app reaches users. Start or schedule a rollout, track milestones, and pause deployment when needed."
When a certified version is available, you'll see:
- Status: "Certified version available for rollout"
- Message: "You will have control and can rollback during rollout process"
- Action Button: "Initiate rollout process"
Step 2: Initiate Rollout
Click the Initiate rollout process button to begin the rollout configuration.
This will take you to the rollout plan confirmation screen where you are shown the rollout strategies available for your app. The rollout strategies possible are:
- Beta Rollout (Full Control)
- Deploy to specific beta users for testing and feedback first
- Recommended for first-time launches and major updates
- Provides full control over user selection
- Lower risk with limited user exposure
Choose the strategy that best fits your deployment goals and risk tolerance.
Step 3: Confirm Rollout
After reviewing your rollout plan:
- Verify the app version is correct
- Confirm the rollout strategy matches your goals
- Click Confirm to initiate the rollout
Cancel Option: You can click Cancel if you need to make changes or are not ready to proceed.
Step 4: Beta Rollout Initiated
After confirming your rollout, the portal displays the beta rollout status screen.
Status Banner: "Beta rollout initiated"
Message: "Invite users for closed beta testing"
Rollout Status: "v1 rolling out"
Rollback Option: A Rollback button is available in the top-right corner, allowing you to revert the rollout if needed.
Invite Beta Users
The portal provides a Beta Enrollment URL that you can share with Ring users to invite them to your beta program.
Section: "Invite beta users"
Description: "Share the Beta Enrollment URL with the Ring users you want to include in your beta test. When users visit this link, they will be asked to confirm their participation in your beta program. This makes it easy to distribute your integration to testers before the public release, without the need to collect email addresses."
Important Note: Maximum 10 beta users are allowed for an app.
Beta Enrollment URL:
https://account.dev.ring.com/account/integrations/accept/invite/beta?appInfo=<encoded_app_info>
Copy Button: A Copy button is provided to easily copy the Beta Enrollment URL to your clipboard.
How Beta Enrollment Works
- Share the URL: Send the Beta Enrollment URL to your selected beta testers
- User Confirmation: When users click the link, they're asked to confirm participation in your beta program
- Access Granted: Once confirmed, users can access and link your app integration
- Testing Begins: Beta users can now test your app with their Ring devices
- Gather Feedback: Collect feedback from beta users to improve your app
Managing Beta Rollout
During the beta rollout phase:
- Monitor Usage: Track how beta users are interacting with your app
- Collect Feedback: Gather insights and identify issues
- Iterate: Make configuration updates if needed (requires new certification)
- Rollback: Use the Rollback button if critical issues are discovered
- Expand: When satisfied, proceed to wider rollout (phased or full)
Step 5: Monitoring and Next Steps
Once beta rollout is active:
- Monitor endpoint metrics and error rates
- Track webhook delivery success
- Review OAuth flow success rates
- Gather user feedback systematically
- Plan for next rollout phase (if using phased approach)
- Maintain ability to rollback if needed
Rollout Strategies
Beta Rollout
Overview: Deploy to specific beta users for controlled testing.
Characteristics:
- User Selection: Deploy to specific Ring users (beta testers)
- Control Level: Full control over who has access
- Feedback Loop: Direct feedback from beta users
- Risk Level: Low - limited user exposure
- Duration: Flexible - continue until satisfied with results
Best For:
- First app launch
- Major updates or changes
- New feature validation
- Pre-production testing with real users
Process:
- Select beta users (typically provided by Ring or your organization)
- Deploy configuration to beta user group
- Monitor usage and gather feedback
- Iterate on configuration if needed
- Proceed to wider rollout when ready
Additional Strategies
The portal may offer additional rollout strategies such as:
- Phased Rollout: Gradually increase user percentage over time
- Full Rollout: Deploy to all users immediately
- Scheduled Rollout: Plan deployment for specific date/time
- Geographic Rollout: Deploy by region or country
Note: Available strategies may vary. Choose based on your app's needs and risk tolerance.
Managing Rollouts
Tracking Rollout Progress
Monitor your rollout through the Developer Portal:
- Rollout Status: Current state of deployment
- Milestones: Key deployment checkpoints
- User Metrics: Number of users with access
- Performance Data: Endpoint health and response times
Pausing a Rollout
If issues are discovered during rollout:
- Navigate to the Rollout process page
- Investigate and resolve issues
- Resume rollout when ready
When to Pause:
- Endpoint errors or downtime
- Unexpected user feedback or complaints
- Performance degradation
- Security concerns
- Critical bugs discovered
Rolling Back
During the rollout process, you can rollback to the previous version:
- Access the Rollout process page
- Select rollback option
- Confirm rollback action
- Previous configuration is restored
Important: Rollback capability is available during the rollout process. Once rollout is complete, you'll need to submit a new configuration version to make changes.
Completing a Rollout
Once you're satisfied with the rollout:
- Verify all metrics are healthy
- Confirm user feedback is positive
- Complete the rollout (if using phased strategy)
- App becomes generally available to all Ring users
Version Control
Review Version History
Access complete rollout history:
Location: Click "Review Version History" in the Version control section
Information Available:
- All certified versions
- Rollout dates and strategies
- Current live version
- Previous versions and their status
- Rollback history (if applicable)
Version Management
Version Tracking:
- Each certified configuration has a version number (v1, v2, v3, etc.)
- Certification date is tracked for each version
- Only certified versions can be rolled out
- Multiple versions can exist (one live, others certified but not deployed)
Updating Your App:
- Make configuration changes in Configure phase
- Submit for certification (creates new version)
- Once certified, initiate new rollout
- New version replaces previous version for users
Additional Resources
- Ring Rollout Process: Official rollout guidelines
Complete Lifecycle Summary
Your app has now completed all four phases:
- Configure: Set up app details, OAuth endpoints, and metadata
- Develop: Implement OAuth flow, API integration, and webhooks
- Certify: Submit configuration for review and pass certification
- Publish: Roll out your app to Ring users
Congratulations! Your app is now live in the Ring App Store and available to users.ext Steps
- Monitor app performance and user feedback
- Plan regular updates and improvements
- Stay informed of Ring platform changes
- Engage with the Ring developer community
- Consider expanding features and capabilities
Last Updated: February 2026
Documentation Version: 1.0.0
Lifecycle Phase: Publish (Phase 4 of 4)
