Camphor

Camphor

Camphor

An advanced AI property search tool

An advanced AI property search tool

An advanced AI property search tool

Project Overview :

Project Overview :

Project Overview :

Camphor is an advanced AI property search tool tailored for homebuyers and real estate professionals. This involves establishing a comprehensive repository of property-related information that can be easily digestible and queried utilizing conversastional language.

Client

:

Shawn Patel and Roshan Srinivasan

Timeline

:

2024 | 3-week agile sprint

Role

:

UX/UI Designer

Team

:

Elliot Beak, James Rayo, Kim Sidhu

The Challenge
How can comprehensive real estate information be effectively simplified to enhance user experience?

Defining the Problem and Project Scope

Our client wants to make it easier for homebuyers to educate themselves about a property and connect with a seller/seller's agent. They believe home buyers should have direct access to residential listings and general property information without having to go through a MLS or title company

Camphor is Democratizing Access to Real Estate Data and Information Across the Entire Residential Real Estate Ecosystem

Identifying the Users
"Purchasing property is a little scary because there's a lot to consider since it's my first time."
"I found sellers did not disclose
information on their property,
this is a huge problem… I had to
discover this through my own
research."

Understanding Casual Home Buyers:
Navigating Real Estate Complexity

Individuals seeking to buy a home, whether for their first time, an upgrade, downsizing, or relocation, may not have frequent involvement in real estate transactions and may lack a profound understanding of the housing market intricacies. They typically approach the home-buying process with a more casual perspective compared to real estate professionals who engage in transactions as part of their business.

Who did we interview?
So we engaged in insightful conversations with 9 individuals who were either in the process of purchasing a home or actively searching for one. We asked our participants about their experiences with property websites, AI-property search engines, and problems the users recognized when searching for properties.
Based on our affinity mapping, some of the key trends revealed that our users:
  • want to be able to discover more about a property in an easy-to-understand way

  • want a more personalized search for characteristics every buyer cares about

  • care about how information is displayed

We then created two personas to help identify Camphor's potential users.

Meet Alex and Sarah

Alex, a first-time homebuyer, needs a way to seek clear guidance and accessible information when it comes to purchasing property. Alex needs a better way to feel confident in making a big decision because he's seen misrepresented properties online.



Sarah, an experienced homebuyer, needs a way to find properties that fit her specific requirements because current platforms don’t offer as in-depth information as she prefers.

Empowering Homebuyers:
Navigating the Real Estate Maze with Confidence

Key Findings

Through our research and persona development, we discovered that users often seek additional insights from real estate agents and frequently struggle to find properties that align with their specific criteria.


Core focus and problem to solve

In today's expensive real estate market, the process of finding a suitable home can be overwhelming and filled with uncertainty. Prospective buyers want assurance about how a potential home will integrate into their work life, accommodate their family, and provide a sense of security. We recognize that home buying is a personal experience.

National language based search is a new feature, therefore most people will not be comfortable using it. So the biggest area of UX is trying to figure out for people to transition from a normal filter based search to a new filter search function. Making the filters understandable and digestible for users that are vising the service for the first time.

How did these insights fall into our scope?

Our Objective

  1. Revise the layout and design of the property report to enhance user readability by incorporating more visualizations

  2. Revising the layout for how filters are organized when a query is made to Camphor search

Mobile-First Approach

Recognizing the abundance of information to present to the user, we opted to begin designing mobile first. This approach allowed us to prioritize the correct information in the initial mobile designs, ensuring seamless transition to desktop iterations while maintaining coherence across platforms

Developer Constraints

But a 3-week spring is pretty short for this project scope, therefore our team discussed what features and functions should be prioritized. We thought of implementing a filters selection feature through the AI chat on the property the user is searching. However, the critical issue was developer constraints: Are these ideas that would not be feasible for a software developer to implement? How do we design placeholders for future branding and creative teams?

Usability Testing and Prioritizing Results

Usability Testing and Prioritizing Results

Usability Testing and Prioritizing Results

Justin carried out a usability test to confirm the effectiveness of the extension. The outcomes were quantified using a graph that assessed both user-friendliness and the user's proficiency in completing the test. The prioritization of results was determined by the severity of identified issues and the potential impact on the user experiencing them.

Justin carried out a usability test to confirm the effectiveness of the extension. The outcomes were quantified using a graph that assessed both user-friendliness and the user's proficiency in completing the test. The prioritization of results was determined by the severity of identified issues and the potential impact on the user experiencing them.

Justin carried out a usability test to confirm the effectiveness of the extension. The outcomes were quantified using a graph that assessed both user-friendliness and the user's proficiency in completing the test. The prioritization of results was determined by the severity of identified issues and the potential impact on the user experiencing them.

What Are the Next Steps?

What Are the Next Steps?

What Are the Next Steps?

In approaching the project, we faced various design constraints but strategically prioritized tasks within the scope of this sprint. Insights received from user interviews expressed that a unique design could have hindered Kindle's overall usability. Adhering to the constraints of an established design system turned out to be a valuable limitation.

In approaching the project, we faced various design constraints but strategically prioritized tasks within the scope of this sprint. Insights received from user interviews expressed that a unique design could have hindered Kindle's overall usability. Adhering to the constraints of an established design system turned out to be a valuable limitation.

In approaching the project, we faced various design constraints but strategically prioritized tasks within the scope of this sprint. Insights received from user interviews expressed that a unique design could have hindered Kindle's overall usability. Adhering to the constraints of an established design system turned out to be a valuable limitation.

In the future, future iterations could include:

  • Adding icons and information about whether the book club is public or private from the book club page list

  • Conduct more usability tests and ask if readers want a limit to member size for public book clubs

  • Explore adding user name to member annotations in the reading annotations tab

  • Design the customizable notification setting for book club alerts

  • And if there are better designs for the reading progress bar.

In the future, future iterations could include:

  • Adding icons and information about whether the book club is public or private from the book club page list

  • Conduct more usability tests and ask if readers want a limit to member size for public book clubs

  • Explore adding user name to member annotations in the reading annotations tab

  • Design the customizable notification setting for book club alerts

  • And if there are better designs for the reading progress bar.

In the future, future iterations could include:

  • Adding icons and information about whether the book club is public or private from the book club page list

  • Conduct more usability tests and ask if readers want a limit to member size for public book clubs

  • Explore adding user name to member annotations in the reading annotations tab

  • Design the customizable notification setting for book club alerts

  • And if there are better designs for the reading progress bar.

Portfolio

Portfolio

Portfolio

Explore Other Projects

Explore Other Projects

Explore Other Projects

Have a Project In Mind?

Have a Project In Mind?

Have a Project In Mind?

Let's Create Together!

Let's Create Together!

Let's Create Together!

Reach out through the form, and I'll respond within the next 24 hours.

Reach out through the form, and I'll respond within the next 24 hours.