Saturday, September 24, 2016

WEEK9

In this week, we had a stand-up presentation to show our process of the project. And I charge for the changes part. Basically, the concept has remained to the initial concept. However, little changes will be taken after last testing session. In total, there three significant points. First of all, we made the change from the high fidelity picture to a more rustic and old fashioned. This is to say,  the image of the product still suit the heritage nature of the recipe, but the pictures are based on two or three simple, complementary colours rather than vivid images. Based on the feedback, most users still wanted to upload the images of their cooked food. Thus the application allows the users upload the pictures, and the pictures will be added to the database as a part of the recipe.  Additionally, the recipes will be presented in the tile layout and use a stylized font to match the heritage style.  Secondly, the functional aspects should be more interactivity simple and user-friendly. We add one more search bar on the homepage. Thus, there is 'search by ingredients' and 'search by recipe' on the homepage instead of solely 'search by ingredients.' Also, the overlay features will be applied to show the preview of the recipe. What is more, a similar overlay could be dot user present the recipe in full screen so that it is easier to read. Furthermore, we optimise the navigational flow to make the choices easier and make the movement with less frustration. On the feedback page, we used the star rating to replace the 'up and down' and allow users to provide feedback through showing changes in ingredients and giving general comments. As mentioned above, uploading images of the meal that was cooked to enrich the database also will be added.  Finally, We have been able to access the Trove API and drawn an excess of over 1000 recipes, and that makes the process slow. Thus, we will limit the numbers of the ingredients and restrict the search results to the top ten recipes. The speed at which information is presented has prompted us to have a spinner that shows the user that the search is still continuing as well. The screenshot is from the presentation slide.
Figure1


On the workshop, we discussed our team logo. I think the logo should represent the theme of the concept. Thus, my sketch is like this.
Figure2


However, the final logo may be other looking, but there will some features referenced my idea.

Additionally, I need to realise the functions of set up and log in. This part also involves the database. Firstly, we need to store the username and their password in our database and need to avoid the duplication of the name. Then, when they log in, the system need to check if the name and password right or not. Thus, we need to ergodic the database. So far I used the HTML to create a form already. Next, I need to know how to connect it to the database.
Figure3

Figure4

The break starts, take a rest and go straight until the end of this semester. Come on!



Thursday, September 15, 2016

WEEK8

On the contact, we tested our paper prototype and digital paper by four users. Before we tested, Trover and I worked on the questionnaire. I help him to organize the questions and set an open question at the end of this questionnaire according to my learning experience. An open question allows the testers to give any ideas/feedback on our prototype. Thus we may get more useful information. Additionally, there will be a happy ending.

After the questionnaire had done, we started the testing session. Here are some photos, which I took when we tested the users. The first user is David; the second user is Nan; the third user is Alex, the last one is Wei Fu.
Figure1. User 1

Figure2. User 1

Figure3. User 1

Figure4. User 1

Figure5. User 2

Figure6. User 2

Figure7. User 3

Figure8. User 4

Figure9. User4

They are all nice, and they give lots of feedback on our prototype. I think the testing session is very successful. However, there are some flaws. For example, we interpret the user serval times. We should let the user finish the testing themselves rather than giving them many instructions. One thing we need to do is observing the users' behaviour, recording the time they cost and making a note of their performance. I think we should improve this in next session. 

I made some notes, but not enough and formal. Here are the photos of my notes. They are a little bit messy. Don't be mind, please.

Figure10

Figure11

Figure12

Figure13

Figure14

We do get some new inspiration to our product. First, the single search bar may become into two search options - search by ingredients and search by recipes on the homepage. Second, the font size may be larger, and the display area may be larger as well. Third, most users confused about the ADD button on the search page. Thus we may add text reminder to it. Fourth, we may change the UP and DOWN-voting into stars rating. Fifth, we may add the ingredient scroll up if there are too many ingredients. Furthermore, I think the minimised design should be involved in our product. 

On the workshop, I discuss the personal website with my tutor. Although this website is more about the content, I will work on one or two JavaScript/Jquery to my website. 

A busy week comes to the end, and another one is on the way! Cheers!


Thursday, September 8, 2016

WEEK 7

At the contact in this week, we discussed our concept with David W and my tutor David. And then, our group get together and work on the core elements/MVP of our product - Gourmandise. Basically, there are four elements, which are search, find recipes, presents recipe and allow feedback/upload photo. We discussed the looking of our product and came up with some ideas for an easy navigation and good-looking application. Here are our outcomes.

     
Figure 1

Figure 2.

Figure 3.

Figure 4.

One effect that we want to achieve is the overlay. When the user clicks on one of the recipes, that recipe will enlarge and appear in front of the previous page. After I research, I find there are different kinds of overlays for different situations. For example, eye candy for displaying your products; snappy overlays for information or warning boxes; modal dialog for prompting and alerting users; tabbed overlays for displaying complex data. I think we need to apply the tabbed overlays for displaying the particular recipe. Like the example below. We can realise the overlay by using jQurey and JavaScript.

Figure 5.

Next, here is the rough sketch of my personal portfolio website.

Figure 6

The home page is very simple, and the down arrow leads the user to the next page by clicking it. The next page has a timeline to mark the 13 weeks. In the middle of the page, there is a display place. For example, if the user clicks on week1, they would get the content of week1 in that place. I may also apply the overlay to realise the display space on my personal website.

On the workshop of this week, we tried to set up to the zones but failed. There may some problem on the back of the server. We already told to the tutor. Thus, we are just waiting for the solution. Additionally, I did not get a chance to discuss my personal website with the tutor because the tutor is too popular so that there are so many people asking him questions.

For next few week, I may continue to work on the functionalities of our application and my personal website.



Friday, September 2, 2016

WEEK6

Time flys by and we come to the end of week 6. In this week, my group members and I gave the presentation of our final concept and we get some useful feedback from the class.  Additionally, we finished our project proposal and polished it and submitted it to blackboard on time.

For the questions about the how to get recipe images from Lorna, I have two possible solutions. One of them is to give the users right of uploading pictures of the ingredients or the meal. However, it may lead to two new issues. One is that there may not be any pictures of some recipes. Another is that if two users upload pictures to the same recipe, that will cause conflict. Thus, we need to develop a new solution to deal with it. Another solution is to import pictures from other websites by accessing their API. Back to the presentation, we just show our vision of this product. We aim to give it a visual aid and make it perfect. No matter which action we take at the end of this question, we will realise the essential functions showed in the presentation of this application anyway.

For the project proposal, I made my effort to the part 2 mainly. I found one existing application - Paprika. I analyse it and indicate what the inspiration we got from it. Also, I specify the difference between it and our product.
Figure 1 Paprika


Figure 2 Paprika

Trevor provides me two applications - Yummly and Kraft I analyse them and give the description as well.
Figure 3 Yummly

Figure 4 Kraft


Moreover, I polished the rest content of part 2 written by Chen. Finally, I upload it to Google drive.

Figure 5


For my personal portfolio website, I come up with a framework. However, I think it is not very good. Thus, I won't post it now. I may post it in next post after development. But have a look at my homepage. This is the first version, I will add more element in it.
Figure 6

See you in next week.