Hover Capture Experience

HOVER CAPTURE EXPERIENCE

Hover Capture Experience

HOVER CAPTURE EXPERIENCE

Company

HOVER

Role

Staff Product Designer

Team

1 PM, 5 algorithm engineers, 3 mobile engineers, 1 data analyst, 1 UX researcher

Timeline

~6 months

01. Context

HOVER uses its capture experience to generate a 3D model and measurements of a home from a few smartphone photos.


Contractors are HOVER’s largest user group, using the HOVER mobile app to measure homes for exterior renovation projects like roofing and siding. When contractors want to bid on projects, they typically visit the homeowner and capture the property with HOVER so that they have a reference to inform their pricing quotes.


One of the challenges in the existing experience was that generating 3D models and measurements often took several hours. The slow turnaround meant that contractors were back in their offices by the time they shared their quotes, thus limiting their ability to close sales while visiting on site.


HOVER saw an opportunity to dramatically reduce the turnaround time of its capture experience by implementing a new algorithm and Simultaneous Localization and Mapping (SLAM) technology — the same tech self-driving cars use to simultaneously sense their surroundings and relative positioning in space.


Implementing these changes would unlock a major opportunity for contractors: the one-call close (i.e. the ability to win sales immediately within a single property visit).


To achieve this, the capture experience needed to be re-built for compatibility with the new algorithm, so I was brought in to own the design of the new end-to-end experience.

"If I could get my measurements back in 20 minutes, I could give a quote right there instead of following up later."
— Contractor

Goal

Working with the new algorithm presented a unique challenge: while it promised much faster generations of 3D models and measurements, it was unproven in its reliability and success rate. Because our existing capture tool was prone to occasional failures as well, leadership was hesitant to risk introducing a frustrating experience.


My challenge was to lead the team in designing a flow that compensated for the algorithm's technical limitations. Our goal was to test whether we could create a new experience that matched or beat the current user experience. Crucially, it also needed to work across all of HOVER's primary user groups: the professionals like contractors and insurance adjusters, plus the homeowners who were often first-time users.

Role & Timeline

I was the sole designer on the Capture team and owned the experience end-to-end. Over course of 6 months, I led UX research and product design up to the second phase of Beta testing:

  • Alpha Testing → 40 professionals (contractors & insurance adjusters)

  • Beta Testing Phase 1 → 500 professionals + 50% of homeowners

  • Beta Testing Phase 2 → 2000 professionals

  • Beta Testing Phase 3 → 20% of all professionals on platform

  • General Availability

02. Alpha Start

To graduate from alpha to beta, the new capture experience needed to perform at least as well as the existing experience. With the current experience, users had to capture at least 9 photos – one for each corner and side.

So how could we determine whether a capture experience was actually better or worse?Qualitative research and interviews gave us directional signal, but we also used a standardized usability metric called UMUX-Lite (Usability Metric for User Experience). It’s a two-question survey measuring perceived ease of use and usefulness, which is converted into a score out of 100. We surfaced the survey immediately after users submitted their photos.

We first measured the existing capture experience with contractors and adjusters and established a baseline UMUX-Lite score of 84.9. That became our benchmark for graduating from alpha to beta.

Initial Alpha Starting Point

The new algorithm relied on visual overlap between consecutive photos to stitch them together into an accurate 3D model.

Before I joined, the team had aligned on an initial instruction: walk in a full circle around the property and take a photo every five steps, meant to ensure enough overlap without asking users to understand how the underlying algorithm worked.

I spoke with six professionals in the alpha testing pool and observed two homeowners capturing their homes. The results were underwhelming.


"“It would be nicer if we could get it to be 10–20 steps [instead of 5].”
“It feels like I’m taking the same photo over and over again.”

Among the 6 pros (contractors and insurance adjusters), 4 preferred the original capture experience, 1 was neutral, and only 1 preferred the new flow.

The quantitative data matched that reaction. The median number of photos taken per property rose from 15 with the original capture to 34 with the new one, and the new experience scored 81 on UMUX-Lite, almost four points below our baseline of 84. More photos was part of the problem, but testing surfaced a few deeper issues with the experience itself.

I spoke with six professionals in the alpha testing pool and observed two homeowners capturing their homes. The results were underwhelming.


"“It would be nicer if we could get it to be 10–20 steps [instead of 5].”
“It feels like I’m taking the same photo over and over again.”

Among the 6 pros (contractors and insurance adjusters), 4 preferred the original capture experience, 1 was neutral, and only 1 preferred the new flow.

The quantitative data matched that reaction. The median number of photos taken per property rose from 15 with the original capture to 34 with the new one. The new experience scored 81 on UMUX-Lite, almost four points below our baseline of 84. More photos was part of the problem, but testing surfaced a few deeper issues with the experience itself.

Some users didn’t read the instructions, resulting in the algorithm not getting the photos it needed.

How might we create engaging and helpful instructions?

How might we design an intuitive, scalable system that helps admins build optimal chatbot flows to increase chatbot resolution rates?

There were moments of uncertainty throughout capture: “Is it OK my car’s in the driveway?” “Am I doing this right?”

How might we increase user confidence?

How might we free up agents’ time by automating simple inquiries, while making it easy for them to step in with context when AI falls short?

After capture, homeowners had no idea when they’d get their 3D model and lacked any sense of closure.

How might we educate the user on what to expect post-capture?

Some users didn’t pay attention to their surroundings, as they were so focused on getting the right shot that they might stumble on a rock or bump into something.

Our business goals were to:

  • Increase Front’s competitiveness in the live chat space

  • Grow ARR directly attributable to the Live Chat product

  • Make Front more mission-critical by helping customers deflect more conversations using knowledge content

Our success metric was to decrease the percentage of chats resolved by a human agent, aiming instead for resolution through the chatbot.

How might we remind the user to stay safe?

03. Alpha Iterations

Improvements during Alpha

Now that we better understood the pain points, I started brainstorming ideas. A lot of the ideas we considered weren't feasible given our technical and time constraints.

Our dream vision, rendered with After Effects

Because of that, the direction our team landed on was to instruct users to take overlapping photos, so the algorithm could more easily stitch them together. Designing the usability of this was challenging, since the technology itself was still being built in real time and was novel enough that patents were being filed on it.

Instructions

Since some users skipped the tutorial before capture, I added in-camera instructions, so guidance showed up right when people needed it instead of something they had to remember from before they started.

Safety

I also added a reminder after the second photo was taken to watch their surroundings, since staying safe while capturing was one of the problems that came out of research.

Confidence

To make people feel confident the app understood what it was seeing, I designed a post-snap AR effect that gave visible feedback that HOVER was intelligent and could read the scene.

Since the algorithm could detect when there was sufficient overlap, I designed the shutter button to pulse blue at that moment, signaling a good time to shoot. We also added a positive sound and checkmark after a good shot for extra confidence.

The Challenge
Choosing how many articles the chatbot should suggest was an important design decision to the user experience. Showing too many could overwhelm the inquirer and make it harder to choose. On the other hand, restricting suggestions too much (e.g. a hard limit of one article) risked a higher probability of failing to show an article that would resolve the inquirer's request.

The Decision
We set the article suggestion limit to three articles max. This offered a balance between giving users meaningful choice and maintaining a high likelihood of resolution. We also planned to monitor real-world usage to determine if we should change this number.

04. Validation

Testing and Feedback

HOVER’s research team had a field trip to Maine planned for a different reason, so I joined them to test the new prototype with contractors and homeowners along the way. I had people try three versions: the original capture, the every-5-steps version, and the new overlap-based method. Almost everyone we talked to preferred the overlap-based method equal to or more than the original.

We saw a few positive themes.

Increased confidence

One contractor, a 6-year HOVER user, told us it was the best way he’d ever taken photos with the app.

“The old system, you didn’t have that confidence that you’re getting all the shots. This one, if you got any smarts about you at all, you can just figure it out that it’s wanting to get that overlap. You just have better confidence in knowing I got that shot.”

People took fewer photos than the every-5-steps version

“I like the overlap even a lot better than the 5-step because I’m lazy… I’m taking about half as many photos as I was trying to do every 5 steps.”

Better for handling obstructions

With the original capture, you had to photograph each corner and side specifically, which didn’t leave much room to work around something blocking the shot.

“Because of the additional pictures, if I have an obstruction, trees, cars, I have a better chance of getting a good view of the house…”

Testing also surfaced four distinct problems

(1) The pulsing button alone wasn’t a strong enough signal.

(2) The instructional text was too small, especially given how far the phone often sits from a user’s face during capture.

(3) Some users thought they had to snap the photo the moment the button started pulsing. In reality, the button could pulse after just one step, since the photos already overlapped, and it might still pulse after ten. Users had a wider window for taking the photo than they realized.

Iterating on Feedback

With those learnings, I added the words “overlap detected” to accompany the pulsing button for greater clarity. I also increased the text size. The pulsing button and label now appeared only after the user had moved a bit, so people took fewer near-identical photos.

With the beta deadline approaching, the researcher and I ran one more round of interviews. All 10 pro alpha users unanimously preferred the new overlap experience over both the original 8-grid capture and the every-5-steps version. We also interviewed 10 first-time homeowners on-site; 9 out of 10 rated the new experience higher.

“If you all go back to the other way, I’m canceling.”

“It is so simplistic, man, I literally couldn’t understand how somebody can’t use this.”

“This… however you guys did it, is way better. The other one (8-photo) was good but… (sighs)… It was more tedious.”

We tested the iterated build with the 40 alpha pros, and it scored 87 on UMUX-Lite, clearing our baseline of 84. That graduated us from alpha into Phase 1 of beta.

05. BETA

Beta Iterations


With the capture experience in a more solid place, I turned my attention to the moments in the flow before and after it.

I directed first-time user instruction videos to replace the old illustrated panels.

My hypothesis was that videos would hold people's attention better than static images, and that watching a real person capture a home would help them understand the process. I also added a video showing how they could snap more photos even when there’s small obstructions in the way. These shipped about two weeks before I left, so I don’t have data on how people responded.

I also updated the post-capture flow. We added a sketch-like 3D preview before submission. We couldn't yet tell whether a capture would succeed, so the preview's job was to show users that HOVER understood what it was looking at. We removed the "Capture Summary" page, an extra step that wasn't addressing any meaningful user need. After users submit their photos, we introduced a confirmation message telling them most people receive their 3D model within an hour. Previously, first-time users had no idea what to expect next and when.

06. OUTCOMES

Beta Outcomes

I left while beta research was ongoing, but before that had the chance to talk to 6 pros.

All 6 pros I talked to in the beta cohort preferred the new capture experience over the original. We also ran a larger A/B test with 500 pros and 50% of all homeowners. Both groups rated the new experience higher, but the gain was much larger for pros than for homeowners.

Original capture: 86 (pros), 74 (homeowners)
New capture: 91.8 (pros), 75 (homeowners)

We also saw a 3.6% increase in capture uploads with the new experience, along with reduced drop-off.

However, there was still more to do as the fail rate also increased by 1.1%, meaning more captures weren’t able to deliver any measurements or 3D models. If I stayed longer, I would have focused on the following problems.

Improving the first-time user experience

Homeowners rated the new experience noticeably lower than pros. Homeowners usually only use HOVER once, while pros use it over and over and get more chances to figure it out. We could focus more on how we could improve the first-time user experience with better onboarding.

Reducing the failure rate

There were UX opportunities to explore for reducing failure, such as clearer guidance during capture. We wanted to experiment with the idea of detecting when the house is cropped in the camera frame, and nudging the user to back up to get as much of the house in the shot. There’s visual affordances that we started experimenting with.