ZooplaQuest

Framing the Problem

What is the problem you are trying to solve? Who does it affect?

- What happened?

- Not enough property = bouncing clients (show demand rates/ pricing trends)

-Failing to agree/Different preferences = frustraction/ bouncing

-Inconvience of sharing links = too long and too much involved

-Not contacting Zoopla in time = bouncing clients

Who this affects?
- House hunters

-Zoopla ( because the process is inconveniencing for house hunters and they lose clients or may get negative reviews)

Idea Explanation

What is your idea? How does it fix the problem?

Our idea was to add a group search feature where we embbed a share code generator for users to have shared access, we also decided on /

Implementation

How do all the pieces fit together? Does your frontend make requests to your backend? Where does your database fit in?

Data Analyst finds out what happened and why, and the team came up with solutions on one of the main issues (Group Sharing) and we offered multiple solutions for this issue. Backend and Frontend coded taskbar and other features to make this work . Designer creates user expeiernce and makes it engaging .

Challenges

What did you struggle with? How did you overcome it?

• -Differences in the group = we communicated and tried to understand everyones reasoning

• -Defining what we wanted to do

• - Connecting backend and front end and getting everyone on the same page

Accomplishments

What did you learn? What did you accomplish?

• Team collaboration ( The importance and value of each player)

Next Steps

What are the next steps for your project? How can you improve it?

• More features to make it more engaging

• Monetizing it through subscriptions or offering help at a price (as their is high demand for property but low supply )

• Live avaliablity of house viewing