Week 12 - End of term presentations (20\01\21)

The moment has come and without noticing we are halfway there. If you stop for a second and look back at what we managed to do in a few months, it is undoubtedly difficult to hide the excitement and team pride that was in our meeting this week.

However, it is clear to us that there is more work to do ahead of the upcoming presentation we have set ourselves several goals:

1. First, we focused mainly on completing the initial prototype following the usability tests we performed this week.

2. Next, we have prepared a presentation that summarizes in a few minutes the entire last period about the following sections:

- Wide context (What do we do, how might we).

- Need validation.

- Our solution.

- Detailed scenario (in essence, the experience top to end). - Videos of user testing.

-Tech architecture.

As can be understood, this was challenging.

3. Lastly, we have prepared a video in advance to present the prototype which in our opinion will illustrate our intention most effectively and efficiently.

Presentation day

The excitement was high, we worked hard, practiced and could not wait to show the initial product to the mentors.

The lecture was overwhelming, fun, and experiential and we were happy to receive comments and feedback for the rest of the process.

From the feedbacks, it is clear that there is more work to be done regarding the design of the screens:

• We need to understand what is the correct way to characterize the apartment profile screen after the search.

• We need to research how to present the rankings correctly and if at all.

• We need to discuss the question of the business model.

• We need to discuss KPI's.

• We need to focus on the MVP of the product so that we can advance to the development stage.

Therefore, as we noted at the beginning the work is not over yet, but what is certain is that we can no longer wait to continue working and maximize the product in the best way.

Week 11 - Low Fidelity Prototype For Our Main User Flow (06-13\01)

finalize our first version of low fidelity prototype, show it to at least 5 users and generate insights that will guide our future versions.

After receiving feedback on the initial design of our main screen in the app - the profile screen, we set ourselves several goals to end the week with a usability test with 5 users, as required.

In order to perform a guerrilla usability test, our main goal this week was to design an initial prototype of the user's main flow in the app, focusing on the onboarding process, the home screen, and the apartment profile.

One of the main challenges in our app is that the screen of the apartment profile necessarily depends on the onboarding process so it was important for us to design the full flow from start to finish, in order to draw the right conclusions from the initial use of the product by users.

The process of the prototype screens was challenging and fun at the same time. On the one hand, for the first time, it was possible to bring everything we had imagined and researched over the past few months into something tangible and working.

However, for the most accurate design of what we expected, we had to think in-depth about the content, the micro-copy, focusing on the main parameters that people mentioned for us in surveys and interviews, and finally unifying everything into a simple and intuitive product.

After the design, we created an initial prototype while combining interactions and transitions between the screens. As we know, this is a preliminary prototype, but it was important for us to give a small taste of the final product by combining vectors, illustrations, and micro-animations in some of the screens.

Later, we performed a usability test on 5 users.

For each test, we met for a zoom video call with the user, sent him the link of the prototype (via Figma), and watched throughout his use of the app. For this purpose, we first presented them with a scenario that they will have to embody:

A student who used to live in a rented apartment in Tel Aviv left it mainly because he was not satisfied with the owner of the apartment and the maintenance, but the environment of the apartment was good in his opinion. He is currently planning to move to a rented apartment in Beer Sheva for his studies. So interested before deciding to get confirmation that the property he found is indeed good.

Apart from the general guidelines, we have asked each user to act as he wishes, there is no correct answer and our goal is to test the product and not him. We asked them during use, to speak loudly and indicate to us their thoughts while using.

It was important to us not to lead users beyond the general guidelines.

Furthermore, in parallel with the design phase, we researched the question of how to obtain the information. One way was to access Facebook and extract information from posts in specific groups by keywords and given a Facebook profile, contact him automatically and get him to fill out a form (google forms for starters).

Following this, we created an initial drawing of the DB (the database where the information will be stored) which at this point relates only to the part of extracting the information from the groups on Facebook.

Pulling out posts from groups on Facebook> For posts that contain keywords, we would like to contact their advertiser> The questionnaire he fills out will create an "ASSET" profile under which there will be criteria with fields of "Rating value" + "Details".

To sum up the week, It is important to note that this week has been one of the most productive over the past few months. The power was high about the time allotted for the task. Therefore, we are excited about the results and full of anticipation for the coming weeks.

Week 10 - Design Our Main Screen (30\12-06\01)

Create a 1st prototype of our main screen , base our main page on our technology research, interviews with experts and technological feasibility

This week we entered the practice phase. We first defined an information architecture that would define the structure and internal organization of the app, in a way that would best serve the users, and make it easier for them to navigate between parts of the system.

As part of defining information architecture, we chose a method of organization and navigation and embedded all parts of the system in it. Information architecture will help system content become more accessible and understandable, define a hierarchy between content components, and streamline workflows within the system.

The continuation of the work process was divided into three main tasks:

1. Analysis articles about User interface

design of similar applications while emphasizing how to present quantitative information, how to create engagement, create an effective incentive, ratings and other common cognitive models.

2. Design the first wireframe of the main screen on them the continuation of the process will be based

3. Research about APIs and tools that will enable us to implement the wireframe technically.

Firstly, on the part of the cognitive research, Noa took command and researched in-depth about articles and studies that examined the successful models of applications of leading companies such as Uber, Get, Glassdoor, Amazon, etc which represent the right model for a good user interface process focused on ratings, reviews and involvement of The crowds.

As a result, several essential guidelines have been raised, attached the document:

https://drive.google.com/file/d/1gX-pd2CrK27HukfoPrzE3mAkGFDNqEza/view?usp=sharing

After a joint meeting and presentation of the above findings, the design team focused on the initial wireframe of one of the main screens in our app. The profile screen of the apartment, where you can see the entire history of the apartments while focusing on the ratings of past tenants.

First, create a moodboard for inspiration whether it is from popular sites like Dribble, Muesli, and Behance or such in apps that are recognized and usable by users.

The profile screen of the apartment, where you can see the entire history of the apartments while focusing on the ratings of past tenants.

For this purpose, we used Figma, which we started working on while dealing with the main questions: how to present to the user most simply and intuitively all the important information and how to catalog it effectively and following existing products on the market and the way the user knows and likes.

Because we deal with quantitative information, one of the guidelines in our work was: present the information in a simple, easy-to-understand, and intuitive way while focusing on reducing the stress that the user is in any way when searching exhaustingly for the information.

Attached the wireframe:

Lastly, we researched APIs to understand what tools we can use to implement our features technically

To sum up the week, we feel satisfied with the work provider, however, we believe it is possible to continue to raise the execution threshold later on.