App Homepage Requirements

Ring Q&A
1

We have a question about the Ring App Homepage requirement.

In our integration, users manage Ring cameras, doorbells, settings, and live view from our mobile app, not from a web application. We do have an HTTPS endpoint for the Ring App Homepage, but today it is just a simple post-link success page.

Would it be acceptable for that page to be a lightweight landing page that:

  • confirms Ring linking succeeded

  • explains that device management happens in our mobile app

  • provides a button or link that deep-links into our app when possible

  • includes browser-safe fallback text for users who do not have the app open on that device

In other words, does Ring expect the App Homepage to be a full web management experience, or is a simple HTTPS handoff page to the partner mobile app the preferred/acceptable pattern when account and device management are primarily mobile-based?

We want to make sure we are implementing this page in the way Ring expects.

2

Hi Darrell,

Good question! Your proposed approach is on the right track, but let me clarify the expectations so you nail it for certification.

The App Homepage should prioritize getting users signed up and into your app as smoothly as possible, regardless of how they arrive (mobile or desktop).

Here’s what Ring expects:

  1. The page should have a clear sign-up option. Even if your product is mobile-first, the App Homepage is where users land after linking completes. The preferred pattern is a web page that allows users to create an account (or sign in), and then directs them to your mobile app. This is because users may arrive from either a mobile device or a desktop browser.
  2. For mobile-only partners, ensure the page handles both contexts:
    -Mobile users: Deep link into your app if installed, or redirect to the iOS App Store / Google Play Store listing if not.
    -Desktop users: Direct them to the corresponding web-based App Store / Play Store page so they can find and install your app.
  3. The page should not be a dead end. A simple “linking succeeded” confirmation alone isn’t sufficient… the user needs a clear next action (sign up, download the app, or open the app).

So to directly answer your question: A lightweight landing page is acceptable, but it should include:

:white_check_mark: Confirmation that Ring linking succeeded
:white_check_mark: A clear sign-up / sign-in option (even if minimal)
:white_check_mark: Smart routing: deep link into your app on mobile if installed
:white_check_mark: App Store / Play Store links as fallback for mobile users without the app
:white_check_mark: Desktop-friendly fallback pointing to the web-based store pages

A full web management dashboard is not required. But the page does need to actively move the user forward whether that’s signing up, downloading your app, or opening it.

Hope that clears things up!

3

Thank you Shay, that does help. I refer you to another question I posted which explains why the sign-up option doesn’t make sense for us: Account Linking Prerequisites