4 ms·
uff. doesn't this depend hugely on context? we regularly eat at lomitz which is a traditional chilean/german place, with the same long menu every day. the it
by andrewcooke 14y ago
uff. doesn't this depend hugely on context?
we regularly eat at lomitz which is a traditional chilean/german place, with the same long menu every day. the items are all famous, traditional dishes that everyone knows (i guess for americans this is like my local diner). pictures would be a nuisance except for tourists.
there's a fancy (but more fantasy/preuvian than "authentic") sushi place up in vitacura that we go to for treats. it's frustrating because they use fictional names without descriptions. pictures would look very nice, i'm sure, but not really help you decide. what they need is detailed descriptions (what would be cool is if you could record what you'd had previously, and your rating, so you can work out what to order next time...)
there's a restaurant up the road that's basically french. reading the descriptions is a pleasure. pictures would be chintzy.
another favourite restaurant of mine is down towards italia; it's russian. pictures there would be great because it's never clear exactly what the description means.
each one is different.
- davemc500hats 14y agoyes it does depend on context; probably diff solutions for diff types of restaurants. that said, can't see how more efficient systems / process would be an inappropriate benefit for almost any of them... even at the high-end, some systems would probably help both customer and restaurant.