Live data from Hacker News

Why are restaurant web sites so bad?

juliansanchez.com

31–40 of 124 posts

Re: Why are restaurant web sites so bad?

#31
Having worked with restaurants before (and having a dad who owns a restaurant), I have come to the conclusion that it's just because most restaurant owners a) just want something that works and is cheap, and b) do not fully understand how web design can help or hurt their businesses.

Bad web designers tend to target restaurants (and medical practitioners) because they have a much easier time selling bad design to them.

Re: Why are restaurant web sites so bad?

#33
Huh. I just realized that I have a strange association between restaurants and their websites.

My expectation of quality is inversely correlated to the quality of their website. When I see a restaurant website that is "good", it makes me thing "chain. corporate. bland. boring."

Re: Why are restaurant web sites so bad?

#34

Because restaurant owners are barely figuring out what email is. How often do you go to restaurant websites vs. actual restaurants (not including Yelp or Google maps)? Truth is, they just don't matter. The cost of creating a website, even a $500 design over a CMS doesn't justify the cost. Also, a small business restaurant owner won't know how to operate a CMS. They just figured out email, remember? Worse, is that web…

Squarespace is a pretty good bet for a modestly computer literate restaurant owner.

Re: Why are restaurant web sites so bad?

#35
Luddite client meets designer who has made their living wowing luddite clients with style over substance.

Also note that movie websites have the same problem. For mostly the same reasons, though the organizations involved and cash transactions are much larger...

Re: Why are restaurant web sites so bad?

#37

One reason for menus in PDF is because the menus may change frequently, and a PDF is easy to create from their actual print menus. It doesn't seem like a big deal to update both an InDesign layout and a website, but if different people do those two things, then it's quite likely a mistake will be made, so it's smart just to use the already proofed version.

I also deal with this while keeping my resume updated and tweaked. I have an HTML, PDF, and MS Word format. I use a print CSS sytle sheet on my homepage (http://ronnie.me) so that I can print it to PDF for the PDF version and manually create the Word version. Very tedious.

Re: Why are restaurant web sites so bad?

#38
post #16

All I want to see are the menu and the hours of operation.

Word. I want the hours, location, phone number, and menu. All in a format I can copy & paste into my email to convince my friends to go. I rarely get any of that at a restaurant's web site. No wonder that it's easier to google/yelp it and use their listings.

That information, if it's there at all, is usually buried in some awful Flash animation.

Re: Why are restaurant web sites so bad?

#39
post #33

Huh. I just realized that I have a strange association between restaurants and their websites. My expectation of quality is inversely correlated to the quality of their website. When I see a restaurant website that is "good", it makes me thing "chain. corporate. bland. boring."

Am I the only person who doesn't mind chain and corporate eateries?

Re: Why are restaurant web sites so bad?

#40
post #32

http://www.onebigmenu.com I'm working on this site right now, and I understand your concerns because I feel them myself. I'm hoping I can bridge the gap between dining and diner. :) (Please excuse the design, since I'm the only developer :P)

I'd advise that you nuke the frontpage. Instead, make it location aware and show categories (ex: recommended, asian, mexican, american, italian, greek, other) with five restaurants each.

The individual restaurant pages are very clean and informative compared to what you might see on a restaurant website. The only things missing are restaurant hours and pictures of food items.

Post reply on HN