Live data from Hacker News

Why are restaurant web sites so bad?

juliansanchez.com

41–50 of 124 posts

Re: Why are restaurant web sites so bad?

#41
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)

That's really cool, I like where you're going with One Big Menu. When I visit a restaurant, I want to know how good what I'm ordering is--I don't care if the restaurant is 5 stars, if what I ordered is the crappiest thing on the menu.

Re: Why are restaurant web sites so bad?

#42
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.

I understand exactly what you're talking about and we now have people inputting hours. I'm going to clean up the front page with things that make sense to people, but right now it's under HEAVY development, and I'm the only developer :P

Re: Why are restaurant web sites so bad?

#43
post #26
post #18

Earlier quoted context omitted.

Touché. Now, just to figure out how to sell our honest and genuine services to them. Cold calling? Anybody with similar experience? I’m genuinely interested.

I think you underestimate the powers that have given rise to the current state of affairs. Ecosystems of sellers usually develop around the characteristics of buyers. Restauranteurs are (as a general rule) terrible buyers and terrible clients. You might look at a site and think "that'll take x hours to do," but you need to factor in the time that it takes to get the client there. In my experience, that's several time…

I see! This must stem from the culture of cheapness that surrounds a lot of restaurants; supposedly the industry is cut-throat.

This just means that the problem needs to be attacked on a different front: marketing. Which is where the hucksters come in...

Re: Why are restaurant web sites so bad?

#45
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)

That's really cool, I like where you're going with One Big Menu. When I visit a restaurant, I want to know how good what I'm ordering is--I don't care if the restaurant is 5 stars, if what I ordered is the crappiest thing on the menu.

I know, and I want to provide a good interface for people to find exactly what they want, when they want. :) And the pictures will provide people with a view into what they're ordering. I think this is the major reason people aren't exploring with dining. :)

Re: Why are restaurant web sites so bad?

#46

I think there are a few things here that cause this: a) You're going against the worst kind of incumbent- the 15 year old nephew or kid next door. He's cheaper, good enough, and "trusted". He is competition that exists a million times over. b) Even if your system is better, they just can't be bothered to even get a good demo. You definitely need to build something so usable and good it's frightening, but good luck ge…

The other problem is going beyond, "hours of operation/location" + "menu" + "phone number" takes integration with on site software. So now your competing with all those Point Of Sale systems.

IMO, there is a huge opportunity for a unified website + POS + Back end software company. But, to step beyond what's out there would take a huge investment.

Re: Why are restaurant web sites so bad?

#47
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)

Oh, also, I'm looking for a designer to help out. So if you're interested let me know :)

Re: Why are restaurant web sites so bad?

#48

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 would be happy if most of the restaurant sites I visit used PDF for menus. They either have nothing, or a badly formatted Word doc that needs custom fonts (no, my install of OSX 10.6 does not have Papyrus, let's keep it that way).

Re: Why are restaurant web sites so bad?

#49
post #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.

That's really neat. Is the CSS file readily available (for others to use), or something you'd prefer not to give out?

(I realize I could probably crawl through the source on your page and just take it, but that seems rude without asking.)

Re: Why are restaurant web sites so bad?

#50
post #49
post #37

Earlier quoted context omitted.

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.

That's really neat. Is the CSS file readily available (for others to use), or something you'd prefer not to give out? (I realize I could probably crawl through the source on your page and just take it, but that seems rude without asking.)

It's as simple as creating a style sheet, targeting items you don't want to print, or create a class such as .noprint, and hide the items with { display: none; }

You'd want to put that CSS in a separate file and include it like this:

The important bit is the media="print". Look at mine all you like, nice of you to consider asking :)

Post reply on HN