Category: Uncategorized

User insights I have learned:

1. I can combined friends’ activity page with search+hot&popular page

2.Timer function is not shown clear

APP MAP:

                                    

Things I learned from prototyping:

1.Saved item is suggested to remove from tabs and have it’s own button floating on the page.

2.Smoothies should combine with recipe. Also, the instructions of choosing the colors are unclear. This week, I designed a CNYK bar which is a pretty intuitive interface for users.

3.Added shop as one of the tabs.

4.During the paper prototyping, my users pointed out several missing “return button”, which I added this time.

week2_map

week2_wireframe

User Insights:

• Bubble icon – user thought that this was a place to chat
• User was drawn to check own profile
  • • Expected an account icon
• Missing back buttons
• Wanted a way to minimize the about section (chef profile) so that it doesn’t take up the whole screen
• Wanted to be able to rate recipe at the bottom of a recipe after making it
• Don’t need a confirmation page for posting a recipe
• User didn’t think settings was important enough to be its own nav item

Old App Map

I realized that a lot of the items that were on my app map were not actual screens, but rather states that occur on the same screen. I also got rid of the settings tab and replaced it with the profile tab, which houses settings.

New App Map

Detailed Wireframes

User insights I learned from paper prototyping

1. Why does “search” deserve a tab? Can it hide inside of the News tab
2. There is no Cart.
3. Why not just show everything in shop, then apply filter.
4. There is no star button in the recipe.
5. There is no buy button in the recipe.
6. There is no price in product detail.
7. This app doesn’t need profile picture.
8. It is not necessarily to create an account.
9. Blenders is less likely to be purchased than those ingredients.

App Map 2.0

Wireframe 2.0

 

Hello! My name is Yao Huang. I’m come from China and graduated from Rutgers University in New Jersey.  My background is Human Resources & Visual Arts. And now I’m the first year student in MFADT.

Three things I don’t know from Apple HIG:

1. Auto-layout
2. Layout Guides and Safe Area
3. Bolder Navigation

Here is my App Map:

Here is my WireFrame:

 

Insights from paper prototyping

The whole app:
Too many functions are mixed, which causes this app complicated.
Home:
1. Give the “Home” tab a name which is related to the content of the tab rather than using “Home”.
2. “Adding to cart” function seems to have the logical problem.
Food Regulation:
The name of “Food regulation” seems to confuse the user, which means that the user won’t think the food shown in this tab is the food the user has at home.
Health Record:
1. How would you get the health data? Could it link to Health app to get part of the data?
2. The layout of this tab is confusing.

App Map 2.0

Wireframe 2.0

User Insights from the first user test

 

 

Sign for the last page of a recipe.
Users were confused about the last page of the recipe because on the step3 page; there was no clue to figure out the page is the final step. Also, users wanted to go back to the main page where they chose a recipe for the first time from the last step of a recipe. But they had to take two steps to go back; which was tapping on a menu and then home button.

 

 

Timer function.
Nobody recognized the timer icon. Users said icon does not look like clickable. The timer is needed when people boil while cooking, but once they click the timer, it should be minimized, so it does not cover recipe photos. Users no need to set the time themselves because based on the recipe, a timer can set it automatically for them.

 

Navigation.
Basically, there is a menu bar on the left to navigate, but has two buttons, which are ‘home’ and ‘my cookbook.’ Users said there is too much blank for the menu navigation, so they suggested me to put those two buttons underneath of the whole interface. Another navigation bar is choosing a recipe based on time. There are three options 5, 10, and 20 minutes. Users said split into three times seemed restricted. Many recipes cannot fit into those three options and suggested me to think about how to make this filter flexible.

 

Based on the feedback, I iterated the prototype.

Below are the second user flow and wireframe.

<First user flow>

<Second user flow>

<Second wireframe>

User insights I learned from paper prototyping

1. PLAN:
   1. It may be unnecessary to set up the number of family members because the family plan has already existed.
   2. Users couldn’t search within the plan to check which recipes are in the plan before they confirm to buy it.
   3. It is hard to know how many recipes are selected in the selection page.
   4. tags may help users to make decisions among the recipes.
2. CURRENT
   1. The processing circle is distractive.
   2. Both horizontal and vertical layout are not that effective.
   3. Ranking feature may be set after users finish cooking.
3. NOTICE
   1. alert rather than notice?
   2. Delivery tracking is necessary.
4. ME
   1. Why users need to connect to their facebook account?

Evaluation from the critique

1. PLAN:
   1. The coexistence of horizontally swiping and vertically scrolling is unclear and confusing.
   2. Users need more obvious trigger to notice that the page could be scrolled down.
   3. Price button may get users give up buying the plan.
   4. users couldn’t preview the details of those recipes.
2. CURRENT:
   1. The processing circle may be not that necessary.
   2. What if users skip one of the day (for example, hang out for the dinner)?
   3. The most important feature on this view should be how to check the recipe that day.
3. SEARCH:
   1. Where do users need to search for something? The position of searching is vital.

App Map V2.0

Wireframe V2.0

3 User Insights

1. User expected something happens after tapping the image and want to view more about the restaurant, such the map, distance, rating and etc..
   

2. Add function “start a plan” (same with facebook messenger) that can add plans to calendar directly when the user invites a friend in the dialogue box.
            
   
3. User wants to see who they went to the places together rather than the posts from others about this restaurant.
   

 

 

 

 

 

 

About Me

I’m Qinwen Xing. My background is graphic design. Most of my previous work are focused on branding, book design, and packaging.

3 things I don’t know from the Apple HIG

1. Apple changed their system fonts to a new typeface “San Francisco” since ios 9.
2. 3D touch gives the user more possibility to interact with contents, such as peek and pop allows the user to preview photos, links, page and etc. It’s important that the peek view is designed big enough so that fingers don’t obscure its content.
3. Make animations optional. When the option to reduce motion is enabled in accessibility preferences, the app should minimize or eliminate application animations.

App Map 

App Wireframe

App Wireframe