Restaurant sites seem to suffer in much the same way as many other industries with typically bad websites (say, real estate, legal firms, and local services). I think this might be due to the difficulty of marketing to small businesses and a general lack of (or perhaps ignorance of) technical savvy.
Thanks for the effort to make local restaurants more "usable" -- this type of endeavor can only help if it manages to catch on.
Or maybe it is because a brick-and-mortar entrepreneur has a completely different mindset from the 'Net Set (so to speak) and it's difficult to see the chasm that separates the two, much less cross it.
There's definitely a market out there that cares about small businesses on the wab, regardless of a business's current mindset, goals, or customer acquisition strategy. Either this market is small or unimportant in some fields, or it's difficult to convince business owners otherwise.
1) Local vs. global audience. I have noticed that websites for local resources tend to miss the fact that their audience on the web is global. If they have a brick and mortar presence and they aren't in a tourist-oriented industry, they seem to just not think about how to talk to a global audience. They often do a poor job of clearly indicating on their website exactly where they are (as in city/state, never mind street address). This probably also influences the lack of "hours" listed on the website. A lot of places have a certain local culture and "everyone just knows" that all restaurants are closed by 11pm (or whatever), with the obvious exception of a few places like Denny's which "everyone just knows" are open 24/7.
2) Staging. On the web, colors, layout, and architecture of information are the equivalent of "staging" of a brick and mortar business. But people who do staging are unlikely to immediately grasp this about web design. I bet there is little or no real communication happening in most cases about how to match the web design to the physical staging so customers get some kind of intuitive feel for the place from the website.
Basically, I think the mindset/mental geography of someone with a brick and mortar business is going to make most small business owners not just technically unsavvy but actually put up road blocks to the kind of thought process and presentation necessary to make a website that would serve their business well.
I hope that's a little clearer.
I bet an algorithm could be built (assuming enough data is flowing) where it automatically adjusts the hours based on when people are checking in. To go along with that, it would show the busiest times, or the "rush hours" based on the density of check-ins at any given time. That's pretty far out there, but with enough traffic flow, you could make predictions and you wouldn't rely on anyone else for that data. You could go further to say "There's a good chance this business is closed because nobody checked in today, and usually there are check-ins."
If you plugged in a calendar, your phone could recommend where to go and when to go to avoid lines. It's like you don't even need to think anymore at that point, just obey the orders your phone gives you.
however, since we're converging on a model that's slightly further toward the 'curated' side of the spectrum than a loopt/gowalla/nextstop, i think we're OK with doing some manual editing of things like open hours, and leaving the rest to the community - all of our community editing pieces aren't out yet (we all still have full-time jobs and/or ambitious clients)...
I love the check-in statistical analysis concept for data generation or at least quality control. very cool for higher volume locations.
We've spent a lot of time on the "Open Hours" feature - we want people to view a page and see "Open NOW", "Open Later Today", "Closed Today", etc. so that they're sure it's really open, or it will be when they take a cab across town, or so its really clear they're closed mondays and you don't go all the way there only to find that out.
However, we also want to be able to search the data ourselves, and we want it to be localized into two or three languages. So we can't just store the open hours as a string, we need to render the open hours as text but it needs to be stored as data. Generating the English/Spanish/Portuguese from the data is a lot of fun.