UX Checklist Scope

Ring Q&A
1

We have a question about how to interpret the UX design checklist for certification.

Some items read like clear requirements, while others seem like they may depend on the type of partner product and flow.

Our integration is mainly a mobile app plus an installed IoT system. We are not offering a Ring-managed subscription, free trial, or a full web-based management experience.

Could you clarify how we should treat that checklist?

Specifically:

  • Which items are required for all partner apps?

  • Which items are conditional depending on product scope?

  • If an item does not apply to our integration, is it acceptable to explain that in reviewer notes rather than implementing it literally?

For example, these seem clearly applicable to us:

  • explaining account linking before redirect

  • showing a confirmation state after linking

  • providing helpful empty-state guidance

  • avoiding technical jargon

But these seem like they may be conditional:

  • emphasizing Create Account over Sign In

  • subscription status and free trial messaging

  • directing users to Ring My Apps for subscription management

  • some tutorial or onboarding expectations

We want to make sure we are interpreting the checklist correctly and focusing on the items that are actually required for our type of integration.

2

Hey Darrell,

You’re reading the checklist correctly, it’s a comprehensive guide covering the full range of partner app types, and not every item applies to every integration.

How to interpret it:

  • Items related to account linking, device display, empty states, accessibility, data deletion, plain language, and your Appstore listing page are required for all partner apps.
  • Items related to subscriptions, free trials, Ring My Apps, and account creation flows are conditional, they only apply if your integration includes those features.
  • Items like tutorials and notification preferences are recommended but should be scoped to match your product.

If an item doesn’t apply:
Yes, explaining that in your reviewer notes is the right approach. Use the “Add notes for reviewer” section during certification submission to call out which items are N/A for your integration and why. The certification team understands that not every partner app has the same scope.

TL;DR: Treat the checklist as “implement if applicable.” Focus on what matches your product, document the rest as N/A, and you’ll be in good shape.

1 Like