Food Scout is an application for travel and food enthusiasts. It caters to the needs of adventurous travelers that wish to enjoy authentic and cultural food experiences on their travels. Existing application review restaurants and give minimal information about the cuisine. One has to do a separate research to find out about a city’s dishes.
One thought on “Food Scout // Presentation 1”
Leave a Reply
You must be logged in to post a comment.
It’d be great if you started your wires off by showing the app map and then labelling the views in your wires with the same number as those you put in the app map. I’m not exactly sure which view corresponds to which right now. It’s also a bit odd the your app map and your views with lines between them don’t match exactly. Which shows more truly all the views in your app and their connections?
Do you think that users will want to search when they are traveling or when they are planning for travel? Either or another option is a valid approach, but I wanted to be clear of your intention.
Saved locations/dishes seem a bit hidden beneath the profile. Is there a better place to put them? What’s the difference between to eat and favorite spots? Are dishes that are saved added to ‘to eat’? If so, then using consistent language there will make it clearer where to find the thing I’ve added. Additionally, the A->Z double stacked picker seems like it will be very hard to every somewhat target the letter I’m aiming for.
Having to enter a city before seeing any content feels like a bit of a hurdle, and isn’t as fun of a way to start the app. How can you bring content to the first view of the app? Perhaps you have featured dishes and/or cities that you show on the first view and the there you can also search to get results for just one city. Or perhaps the main interface of the app is a map, showing results wherever the map is centered with different colored pins for breakfast/lunch/dinner. Or maybe something else, but bringing up content earlier is key.
How do you go back from the dish detail view to the list of all dishes?
The call to action to find this dish is so important, I’m wondering how we can raise the importance of that and again bring some content up. Perhaps you can list 3 places in town that are known to be the best regardless of location and have a button for seeing more places. Also realistically, how many places per city would have the dish? Perhaps you don’t even need the additional view where I see all the locations on a map.
If you keep the map view, you don’t need to have the slider, you can just show results in the region that the map shows, perhaps with an ability to re-search if you drag over the map. I’m also wondering if the price selector needs to be persistent, or should be hidden when not in use to give more space to the map. Likewise, you may want to explore having the restaurant detail page be it’s own page instead of floating on the map. If you keep it floating on the map, make sure it’s clear how to close it or make it where it can be open with the map open and usable at a smaller size.
I’d suggest keeping away from social in the app until you nail down the individual user’s journey a bit further.
Keep on!