One thought on “Furu Iteration 1(App Map & Wireframes)”
We spoke about this a bit in class, but I think focusing on the experience of planning for a food focused trip, or at least a trip where food is important, will be helpful as you keep iterating.
On your app map, generally your most important tab is your first tab, so I’d make 2.0 Food the first tab. Additionally, you likely have pages that are under Favorites. The Favorites main view will likely be a list of favorite items that then you tap to see their detail view.
We also spoke about this in class, but even in your wires, it’s important to make it clear what tab I’m on at any time. I assumed that we were on the favorites tab, when we were really on the Food tab.
Integrating power user features, like the hidden swipe could be interesting, but make sure that they’re serving a big purpose. If you can just tap the item and go to the detail, why have another button that doest that? Explore having top level big choices there, perhaps adding to favorites.
On 2.1 Food info, make sure that your buttons are clear and easy to use. The play the audio button makes sense to me, but I’m not sure what the plate icon means on first glance. Also, taking people to restaurant information is a key part of your app, so making sure people do that is essential. In that same vein, is it necessary for the user to navigate to go to the list of restaurants? At very least, could you give a preview of a few places that have this dish and then navigate if you want to explore more detail?
Do I only see a map on the favorites tab? At very least, it’d be nice to see a restaurant I’m considering on a map.
I believe we finished with this in class, but you’ll need to explore how I even indicated that I’m going to a particular location. Can I have multiple upcoming trips that I’m planning for? Having just one set location in settings seems cumbersome. How can you make that experience easier to manage?
Instead of delete on Favorites, it’s more ‘remove from favorites’. Delete makes it sound like you’re removing it from the entire system.
You can save information without having a log in, so I’d suggest against that for now, or as we talked about integrate that as something users can optionally do to sync their information across devices and the web.
We spoke about this a bit in class, but I think focusing on the experience of planning for a food focused trip, or at least a trip where food is important, will be helpful as you keep iterating.
On your app map, generally your most important tab is your first tab, so I’d make 2.0 Food the first tab. Additionally, you likely have pages that are under Favorites. The Favorites main view will likely be a list of favorite items that then you tap to see their detail view.
We also spoke about this in class, but even in your wires, it’s important to make it clear what tab I’m on at any time. I assumed that we were on the favorites tab, when we were really on the Food tab.
Integrating power user features, like the hidden swipe could be interesting, but make sure that they’re serving a big purpose. If you can just tap the item and go to the detail, why have another button that doest that? Explore having top level big choices there, perhaps adding to favorites.
On 2.1 Food info, make sure that your buttons are clear and easy to use. The play the audio button makes sense to me, but I’m not sure what the plate icon means on first glance. Also, taking people to restaurant information is a key part of your app, so making sure people do that is essential. In that same vein, is it necessary for the user to navigate to go to the list of restaurants? At very least, could you give a preview of a few places that have this dish and then navigate if you want to explore more detail?
Do I only see a map on the favorites tab? At very least, it’d be nice to see a restaurant I’m considering on a map.
I believe we finished with this in class, but you’ll need to explore how I even indicated that I’m going to a particular location. Can I have multiple upcoming trips that I’m planning for? Having just one set location in settings seems cumbersome. How can you make that experience easier to manage?
Instead of delete on Favorites, it’s more ‘remove from favorites’. Delete makes it sound like you’re removing it from the entire system.
You can save information without having a log in, so I’d suggest against that for now, or as we talked about integrate that as something users can optionally do to sync their information across devices and the web.