wk04_Stella

Among all the feedback, what tangled me most was the process of how users select and buy a weekly plan in the app. Initially, I just considered it as a normal buying process, however, during the user tests, I noticed that there are many other factors which should be taken in my consideration. For instance, how to encourage people to buy again? Or how to differentiate various plans with each other? Therefore, I did a redesign of Order-A-Plan.

digital prototype

Week 4

User Insights:

  • Wanted to be able to see more stuff under explore without scrolling
  • Feed and discover look too similar
  • Users swiped through the steps of the recipes and didn’t use the next button
  • Users wanted play button to be centered on video
  • More blur behind titles to make them more legible
  • Add steps to making a recipe instead of putting it all on one screen

Updated Prototype

Week4_Ting

User Feed Back

Structure
1.Two floating buttons are weird. Need to decide whether search or saved item is more important to have an individual tab. In this case, search seems more important; I decide to keep saved item in the profile tab.

2.News tab > Inspairation

3.Missing sub-category page.

4.In the Profile tab, the food preference tags seem unnecessary.

5.Pantone color smoothie: kept only the “Brightness” slider to restrict users picking from yellow, orange, green, and purple color scheme (because not all the colors can be made by smoothies.)

Design
1.The background color for tabs shouldn’t be the same color as the app background, and the highlight color pink is unclear.

2.In the full recipe page, steps instructions in the bottom change to slide show, following step by steps by swiping left.

3.Bigger bigger bigger!

4.The plus sign next to products in shop tab are confusing.

5.Remove the cart logo and show “4 items in cart” with text  on the upper right corner.

Week 2_Jean

User Insight/ first paper prototype

 

  1. Should allow the users to select each ingredient before they add it to the shopping list, just in case they already got that ingredient.
  2. In the “Shopping list” page, it should have “add” button, just in case the user wants to add some other ingredients to there shopping list. Also, the “done” button can be added, for them to use after they have finished all the shopping.
  3. The “method” part is confused because it does not show full method at the beginning. It should provide a full method in the main recipe page.
  4. About the timing in the “Full Screen Recipe” part, a timer should pop-up in that page after the user tap on the word. In order for the user to see when the time is running.
  5. The recipe page and the restaurant page are the same, should do something to differentiate this two page. Instead of showing the time/price/calories in the restaurant page, it can be the brief description of the restaurant.

 

Second Wireframe

WK3&WK4_YIN HU

Insights from WK3 prototyping

Dishes tab:

(1) If the user wants to take dishes from the Not Recommended category, perhaps there is a reminder.

(2) Change the pattern of the changing the dish’s number’s button.

Me tab:

(1)Think about reorder function, such as reminding the user to reorder it, or setting to reorder it automatically

(2)What’s in the setting?

(3)Scanning medical records, the confirm button is not necessary

Others:

Since dishes of the homepage is sorted by health records, it might be better to remind users to update their health records.

Visual Design 3.0

the digital prototype

 

Week 4 – Franky Wang

User insights for the digital prototype on Feb 15th

1 – In the post page of dish categories, there is no need to separate posts into two parts of “all” and “following”. Because in the 3rd level page, users do not tend to figure out the differences according to their specific interests on uploaders. In this case, it is reasonable to list all the posts.

2 – Detail problems:

(A) The back button and edit button in the post preview page are repetitive, so I deleted the back button.

(B) The restaurant page will be more helpful if includes more information, like opening time, reservation status, etc.

 

 

 

 

3 – If possible, try to figure out more intelligent functions like employing automatic recommendations (according to previous searches), photo recognizing (for filling out information automatically) using AI or big data technology.

Week 3 and Week 4

Then on week 4, I created a digital prototype:

https://marvelapp.com/3ii0b8f/screen/38231618

Insights from week 3 paper prototyping, presentation, week 4 digital prototyping:

  • When meals are already chosen how do you go back to edit them
  • The differences between planning and eating the meals
  • Looks like a Clinics app, because it’s a baby’s food app it can look warmer
  • Milk intake measurements is still confusing
  • If the user has more than one child
  • The weight goal of the baby can be in the Baby data
  • When creating project in Marvel should make it clickable throughout and not a linear journey