On your app map, I’m a little unclear why there are different pages with slightly different variations on things. I think that in class you just presented the first one.
I know you said in your presentation to not worry about the page with the design element of the typographic treatment of the word chef, but I’d say that’s significant. In general, app users want to get to content as quickly as possible, and that feel a bit like a splash screen that is getting in the way of users getting to what they most quickly are going to want to accomplish: access an existing recipe or add a new recipe. Additionally, there’s generally no need to include an app title or logo inside of an app, as to get there a user had to tap on the app icon on the home screen that has that information.
We talked about this in class but there really seem to be only two major flows that need to exist in your app, accessing existing recipes and adding new recipes. The camera or what is called the image gallery in your app map can be incorporated into your other sections.
We also talked about this, but while browsing by category seems useful, letting people search for exactly what they want from the beginning makes sense. If I know I’m making “Mammaw’s Chocolate Birthday Cake”, there’s no need for me to have to go thru to a dessert section and then to search, I should just be able to search for that directly. You could also let people add tags to their recipes that could be searchable.
It’d be worth looking at cookbooks or recipe binder organizers or other recipe taxonomy systems to see which browsing hierarchy you believe will be the most useful for people. The box of recipes I have from my mom is just by first letter. Maybe you let people sort and filter by different criteria as well.
In browsing or search, how can you make those table rows as useful as possible? What type of images and information can you provide at that level to help a user make the decision of if that is a dish worth making? A picture, the name, perhaps the time of cooking, and other details could all be useful.
You also need to think through the process of adding a new recipe more fully. Can you take people step by step in some way to get the information you need to compile a recipe? It’s worth noting that the recipe creation mode could differ from the recipe viewing mode.
I’d suggest taking two recipes, one simple and one complicated and laying out those recipe. How can you lay them out in a way that is useful on a phone? You could download a bunch of different recipe apps and see how they accomplish this. Many people have approached it in different ways.
Overall, step back and reemphasize those two main purposes of viewing and adding new recipes. Make sure the viewing/browsing experience is easy and delightful. Make sure that the adding of new recipes is as easy and quick as possible.
Grace Anne Foca
Jun 18, 2014 @
15:46:09
I actually have made quite a lot of changes since class and was going to post my updated wireframes today! Thank you so much for this feedback, you will find in my newer wireframes that a lot of these changes have been implemented.
Jun 18, 2014 @ 15:39:59
Hey Grace Anne,
On your app map, I’m a little unclear why there are different pages with slightly different variations on things. I think that in class you just presented the first one.
I know you said in your presentation to not worry about the page with the design element of the typographic treatment of the word chef, but I’d say that’s significant. In general, app users want to get to content as quickly as possible, and that feel a bit like a splash screen that is getting in the way of users getting to what they most quickly are going to want to accomplish: access an existing recipe or add a new recipe. Additionally, there’s generally no need to include an app title or logo inside of an app, as to get there a user had to tap on the app icon on the home screen that has that information.
We talked about this in class but there really seem to be only two major flows that need to exist in your app, accessing existing recipes and adding new recipes. The camera or what is called the image gallery in your app map can be incorporated into your other sections.
We also talked about this, but while browsing by category seems useful, letting people search for exactly what they want from the beginning makes sense. If I know I’m making “Mammaw’s Chocolate Birthday Cake”, there’s no need for me to have to go thru to a dessert section and then to search, I should just be able to search for that directly. You could also let people add tags to their recipes that could be searchable.
It’d be worth looking at cookbooks or recipe binder organizers or other recipe taxonomy systems to see which browsing hierarchy you believe will be the most useful for people. The box of recipes I have from my mom is just by first letter. Maybe you let people sort and filter by different criteria as well.
In browsing or search, how can you make those table rows as useful as possible? What type of images and information can you provide at that level to help a user make the decision of if that is a dish worth making? A picture, the name, perhaps the time of cooking, and other details could all be useful.
You also need to think through the process of adding a new recipe more fully. Can you take people step by step in some way to get the information you need to compile a recipe? It’s worth noting that the recipe creation mode could differ from the recipe viewing mode.
I’d suggest taking two recipes, one simple and one complicated and laying out those recipe. How can you lay them out in a way that is useful on a phone? You could download a bunch of different recipe apps and see how they accomplish this. Many people have approached it in different ways.
Overall, step back and reemphasize those two main purposes of viewing and adding new recipes. Make sure the viewing/browsing experience is easy and delightful. Make sure that the adding of new recipes is as easy and quick as possible.
Jun 18, 2014 @ 15:46:09
I actually have made quite a lot of changes since class and was going to post my updated wireframes today! Thank you so much for this feedback, you will find in my newer wireframes that a lot of these changes have been implemented.
Jun 18, 2014 @ 16:58:14
Good deal. Will check it out!