3 ms·

I'm really happy that you have addressed this problem. My question comes down to, in the rating process, I rated a fairly limited amount of places, in terms of

I'm really happy that you have addressed this problem. My question comes down to, in the rating process, I rated a fairly limited amount of places, in terms of categorical scope. Then when I moved into the main application, there were many many more categories available, like ice-cream and bbq. I found myself not finding restaurants that I liked loading in the initial 10 choices, so I kept skipping a lot. You might consider a continuous scroll feature for this initial rating set. Otherwise, integrate with open table, and this will rank as the best vertical search/discovery app I've ever come across.

schiff 15y ago
Guimarin, Thanks for the feedback. We made a slightly different mechanism for rating on the personalize page (the list of places you saw when you first came to the app allowing you to quickly rate). Either a user can skip a place manually by clicking the X, or can scroll down to the bottom and skip all the places that you don't like. You are saying you would rather just scroll past the ones you don't know? -Jeremy
- perfmode 15y ago
  Many apps made these days make use of infinite scroll. Users are getting used to this style. If the purpose of the Skip All button is to compile a list of restaurants the user has not yet visited, and if this information is sufficiently useful such that you don't want to get rid of the button altogether, perhaps consider a happy medium: for instance, a Skip All of the Above button placed between every ten restaurants on an infinitely scrolling list. I, for one, think the scroll down -> skip all -> scroll down -> skip all design is clunky--especially since I've visited less than 5% of the restaurants presented at any given time.
- guimarin 15y ago
  Yes, that's exactly what I'm saying. I don't know if I agree with the other commenter about interspersed skip alls. For me, scrolling past seems less final then hitting skip. If I hit skip, I was afraid that a negative mark would be given to the restaurant. I know that's not the case, but it was a very strong incentive for me not to want to hit skip, or the x. I didn't feel like harshly judging a place that I'd never been to.

schiff 15y ago

Guimarin, Thanks for the feedback. We made a slightly different mechanism for rating on the personalize page (the list of places you saw when you first came to the app allowing you to quickly rate). Either a user can skip a place manually by clicking the X, or can scroll down to the bottom and skip all the places that you don't like. You are saying you would rather just scroll past the ones you don't know? -Jeremy

perfmode 15y ago
Many apps made these days make use of infinite scroll. Users are getting used to this style. If the purpose of the Skip All button is to compile a list of restaurants the user has not yet visited, and if this information is sufficiently useful such that you don't want to get rid of the button altogether, perhaps consider a happy medium: for instance, a Skip All of the Above button placed between every ten restaurants on an infinitely scrolling list. I, for one, think the scroll down -> skip all -> scroll down -> skip all design is clunky--especially since I've visited less than 5% of the restaurants presented at any given time.
guimarin 15y ago
Yes, that's exactly what I'm saying. I don't know if I agree with the other commenter about interspersed skip alls. For me, scrolling past seems less final then hitting skip. If I hit skip, I was afraid that a negative mark would be given to the restaurant. I know that's not the case, but it was a very strong incentive for me not to want to hit skip, or the x. I didn't feel like harshly judging a place that I'd never been to.