It’d be great to see your views numbered the same as your app map so that I can easily see where each belongs.
First like we talked about in class, clarify your user a little bit. It’s fine to build your entire system off of Yelp bookmarks. If that’s the fact, then there’s no reason to build an entire Yelp-like system for finding additional bookmarks. If so, then I suppose you can argue that someone would have to login to use the app, but it’d be nice to show the user in some way what the value of the app was. Perhaps you can show close by places with reservations available or some other content, but I’m not sure it’s worth figuring that out.
We spoke a bit about your tab bar in class, but I can’t remember exactly where we landed. Keep in mind that you’re always in one of your tabs and even on a wireframe should indicate which tab you’re on.
You’ll want to flesh out more what the ‘information’ is for each restaurant. What kind of information could you give to help your user make a decision to eat there? When are they likely looking for, to eat tonight? Or this weekend? Or right now?
There would need to be several more steps between picking a restaurant and finalizing a reservation. You’d need to tell the restaurant when you’re going and how many people are going with you. Speaking of, that would be useful information to be able to filter by on the main view. Perhaps you want to go out to dinner with a group of 6 friends, that’d probably change the restaurants that you’d be able to go to.
Once you figure out that interface in a bit more detail, we may want to explore other ways that we can encourage you to go to restaurants that you’ve bookmarked. Can we reward you in some way? Can we show you other friends that have similar place bookmarked? Push notifications? But don’t worry about any of this until your main flow is much more fleshed out.
You should think through the real content necessary for your bookmark detail page instead of just having placeholder blocks of text. What would your user want to know to make their decision about what place they want to go to?
I’ll probably also need a place to see any reservations that I do book.
You’re going to need to add many more details as you move into your next iteration.
It’d be great to see your views numbered the same as your app map so that I can easily see where each belongs.
First like we talked about in class, clarify your user a little bit. It’s fine to build your entire system off of Yelp bookmarks. If that’s the fact, then there’s no reason to build an entire Yelp-like system for finding additional bookmarks. If so, then I suppose you can argue that someone would have to login to use the app, but it’d be nice to show the user in some way what the value of the app was. Perhaps you can show close by places with reservations available or some other content, but I’m not sure it’s worth figuring that out.
We spoke a bit about your tab bar in class, but I can’t remember exactly where we landed. Keep in mind that you’re always in one of your tabs and even on a wireframe should indicate which tab you’re on.
You’ll want to flesh out more what the ‘information’ is for each restaurant. What kind of information could you give to help your user make a decision to eat there? When are they likely looking for, to eat tonight? Or this weekend? Or right now?
There would need to be several more steps between picking a restaurant and finalizing a reservation. You’d need to tell the restaurant when you’re going and how many people are going with you. Speaking of, that would be useful information to be able to filter by on the main view. Perhaps you want to go out to dinner with a group of 6 friends, that’d probably change the restaurants that you’d be able to go to.
Once you figure out that interface in a bit more detail, we may want to explore other ways that we can encourage you to go to restaurants that you’ve bookmarked. Can we reward you in some way? Can we show you other friends that have similar place bookmarked? Push notifications? But don’t worry about any of this until your main flow is much more fleshed out.
You should think through the real content necessary for your bookmark detail page instead of just having placeholder blocks of text. What would your user want to know to make their decision about what place they want to go to?
I’ll probably also need a place to see any reservations that I do book.
You’re going to need to add many more details as you move into your next iteration.