Skip to content

Stand‐up two

Ah!!!!!!!!!!!! edited this page Oct 27, 2023 · 3 revisions

Week10 - Week12

This page will show what we did before stand-up two (week11) and tradeshow (week13).

Week 10

This week we started with a second user test (User evaluation) based on the mid-prototype to summarise and update our design. After this work, the team started to prepare for the final high-fidelity prototype, and by the end of the week we had finished collecting the pre-production materials (text descriptions of the products in the app, pictures).

User test (User evaluation)

User test Aim:

Compare with last Think Aloud test for low-fidelity prototype, this new testing session for our mid-fidelity prototype mainly expect to find out users’ thoughts on the prototype theme styles, word usage ( ways of expression on different functions or buttons) of our current user interfaces, at the same time looked for suggestions and reflections from participants about the functioning setting in our prototype. Users are welcome to provide suggestions for us to improve the prototype as well.

User Test setting:

Compare with last testing session, this test we only invited 3 participants and asked them to click around the mid-fidelity prototype individually. We asked users to click each of the buttons to view through different pages and record their impressions and feedback of our current prototype using Miro board.

test results:

We found three participants to do the user evaluation of our mid-fidelity prototype mentioned above. We used Think Aloud method to ask users click each of the buttons to view through different pages and record their impressions and feedback of our current prototype using Miro board. The results are shown below.
user evaluation results

New design implications

From the think aloud user test, we found that users are somewhat clear about what our application is about. For example, they could understand that our app allows user to use group order to purchase healthy food in cheaper ways, and they think the overall design style of our interfaces is comfortable. However, there are some features in the prototype that causes confusion from the participants. For example, users are not understanding ‘find health’ in the map interfaces, and they are not understanding how to join group order as there are no detailed page to demonstrate this interaction process.
Based on the user test and findings, we have drawn a few design implications:

  1. Change terms easier for user to understand.
  2. Show delivery status
  3. Change map title "find health" - " find healthy restaurant"
  4. Add function of selecting preferable materials in box.
  5. Make group order function clearer. In future progress, there are also some possibilities for us to improve the prototype, includes:
  6. Research function that allows user to find their food directly
  7. New features in the map page to make it compatible with existing apps on the internet.

New iterated mid-fidelity prototype

Based on the user tests and design implications summarised last week, we iterated the mid-fidelity prototype and improve it.
detailed in mid-prototype

Assets Finding

Firstly, since our app mainly allow users to buy healthy food product together with other users or individually, we absolutely need various assets to show the detail of each food product.
We found the Mediterranean diet among many healthy diets as the main healthy plan of our app, and we found each asset based on what is included in a Mediterranean diet. For example, as images shown below, almond is a kind of raw food material that could be included in Mediterranean diet, so we found the royalty free image of almond and using one simple sentence to describe the benefit of almond, and document all the references of our asset resources.

Example:

Asset example

Week 11

This week, we iterated over the Mid-fidelity prototype again and basically implemented the code required for the project

Second Iteration

We conducted the final iteration of the prototype based on the feedback received from previous evaluations.

  1. Firstly, we changed the presentation of the restaurant interface. From the original big map to a restaurant list, clicking on the list will display the specific location of the restaurant.

  2. Secondly, we have added progress display for express delivery. Users can learn about the transportation status of the items they have purchased on the relevant pages.

  3. Thirdly, we have added a function to display the number of users who have already purchased in the item details interface. Through this function, users can have a clearer understanding of the current order consolidation situation

Second Iteration 1 Second Iteration 2 Second Iteration 3

Coding

This is a partial presentation of the HTML. We finished building the front-end framework based on the prototype diagram. We have implemented the three main features we expected to show:

Three main function:

  1. Users can view all the healthy diets offered by the app through the shopping page of the app and can add them to the shopping cart to place an order.
    1. User can see which items the app have in the Shopping page:
    Shopping page
    2. User can choose between two different oder options(individual or group):
    item page
    3. The total pice will show in the cart page:
    Cart page
    4. The delivery page will show all oder progress:
    Delivery page
  2. the app can recommend cheap and healthy restaurants in the neighbourhood based on the user's location.
    1. Restaurant page will show nearly restaurants:
    restaurant page
    2. Map page will show the exact location:
    map page
  3. Users can use the chat function provided by the app to share insights on healthy eating and ways to save money, as well as share the address of the restaurant to find like-minded people to dine with them.
    1. Chat list will show all cost of living Group Chat:
    chat list
    2. Users can share their money-saving experiences or find users who are looking for a group buy together in the group chat. There is also the possibility to find users who want to go to a restaurant together.
    caht page

Some HTML code:

Week 12

Poster:

We mainly display three aspects in the poster

  1. Firstly, it is our problem space and target audience.

  2. Secondly, we provided literature support and our own interviews and surveys, and the data obtained reflects that our target users indeed have relevant needs to be met. We also considered the functions and ethical considerations that the application should have, laying the foundation for subsequent high-fidelity prototypes and final products.

  3. Finally, we presented the results of each iteration along the timeline, clearly explaining each change and improvement of the team.

poster

Powerpoint:

Powerpoint page 1 Powerpoint page 2 Powerpoint page 3 Powerpoint page 4 Powerpoint page 5 Powerpoint page 6 Powerpoint page 7

Flyer:

flyer 1

flyer 2