Introducing an autonomous camera into the home

I pioneered the UX for Ring's autonomous flying camera, navigating the tension between high-tech capability and domestic trust.

TLDR

• The Spark — A 15-Minute Coffee

  A PM and a TPM were already nerding out over Lidar and spatial technologies. They had the “what”; they just needed the “how.” By 1 PM, a random invite hit my calendar, and I was brought in as the founding designer to help turn that ambitious technical vision into the Always Home Cam.

• The Challenge — The Trust Deficit

  Early usability research revealed a pattern: users were excited by the concept but hesitant at setup. Privacy is at the core of everything Ring builds, but this project pushed that commitment to its limit.

• The Strategy — Mapping Uncharted Territory

  No competitive benchmarks. No existing patterns to borrow. Should we look at robot vacuums? Or perhaps video games? We were designing a new category from the ground up, which meant every assumption had to be tested with real users in real homes. My PM and TPM colleagues pitched me a 15-minute coffee chat; instead, I got to define the mental model for indoor flight.

• The Impact — As Seen in SF

  I helped define the product requirements and early vision, building out every core flow, from Lidar setup to recording flight paths. As the project gained traction across Ring, my prototypes became the standard tool for securing stakeholder buy-in. It all culminated when our work spearheaded Amazon’s 2020 Devices conference. Just like in the movies.

A camera that flies. Inside your house. Now what?

Ring Always Home Cam was unlike anything we’d shipped before, or that users had ever experienced. A drone that autonomously navigates your home raises immediate, visceral questions: Is it watching me right now? Who controls it? What happens if it crashes? We had to design trust from scratch.

Existing mental models for home security cameras didn’t apply. Stationary cameras are passive. This one moves, makes noise, and makes decisions. The UX had to carry the full weight of explaining a fundamentally new product category.

Mapping the path: from unbox to first flight

Systemic scale, blurred for Legal’s sake. These journey maps cover every edge case of the ecosystem, from initial setup to long-term retention, at a resolution my NDA can live with.

When our POC went viral internally, design thinking by the books was no longer an option. Try telling a VP they can’t announce a potential flagship product because you need 6 months of deep research. Is building personas on assumptions ideal? Not quite, but c’est la vie. In high-stakes product launches, waiting for “perfect” data is a luxury you can’t always afford. We moved forward with what we had, knowing that the real test would happen in the field. We pivoted, leveraging existing personas and internal data to map the journey at lightning speed.

Setup is the product’s first impression, and for Always Home Cam, it was the highest-stakes moment in the entire experience. Users needed to understand what the camera does, where it will fly, and how they remain in control, all before they’d seen it move a single inch. Working with UXR, we ran contextual inquiry sessions in users’ actual homes. We needed to understand the physical environment. The result was a setup flow designed around progressive disclosure: earn trust before asking for permissions, explain before demonstrating, and always give the user an escape hatch.

Building trust: A. Privacy-first setup slideshow. B. Consistent copy reinforcing autonomous flight. C. Low-stakes onboarding to master controls before the first real flight. D. Proactive callout cards for transparent error handling and system status.

Designing for control in a live environment

Once set up, the ongoing experience had to make users feel like the camera worked for them, not the other way around. Live view, flight history, and path management became the three pillars of the ongoing UX.

• Flight history and accountability

  Every flight is logged. We designed a timeline UI that made this feel like a feature, empowering users to audit, instead of just observing.

• Mapping editing post-setup

  Life changes, furniture moves, kids grow. We built our mapping tool with the possibility to add multiple viewpoints or landmarks, and add as much as 10 different paths. Your entire house would be covered.

• Shared access

  Multi-user households introduced a new layer of consent logic. Who can launch a flight? Who sees the history? We designed a permissions model that respected household dynamics without requiring a CS degree to configure.

• Failure states as trust moments

  The camera will fail: obstacle detected, low battery, dock missed. We designed every error state as an opportunity to reinforce trust. Clear cause, clear recovery, no blame.

Learning that you can't win them all

We tested the UX and polished product with ██████ testers. Testing data told a clear story: users who completed setup converted to active daily users at a ██████ higher rate than our baseline. People reported using the camera to check in on their animals, check whether their kitchen stove was on or off, or if doors were left open; total automation of peace of mind. The omnipresent trust model worked and testers who understood the camera before first flight were far less likely to return it.

Is it frustrating to work on a flagship product that you can’t yet buy? Absolutely. But in high-stakes hardware, the “messy middle” is where the cool things happen. I learned to negotiate with Legal when the UI felt too intrusive, to pitch a vision to Jamie Siminoff, a CEO who has seen it all, and to accept that sometimes, the most brilliant work stays behind a “Redacted” curtain for a while. This project was about category creation. I left Ring with a new mental model for trust and the certainty that if I can design a UX for a flying camera in a living room, I can handle whatever weird challenge comes next.