top | item 9616275

Ask HN: Did you implement a lunch picking app at your startup?

26 points| hrayr | 10 years ago | reply

When a group of developers start meeting regularly for lunch, it's almost inevitable for them to create an app -- within days -- to answer a real question: What the heck should we eat today?

This happened to me on more than one occasion. Here's an old one from where I worked at long time ago: http://www.venarc.com/lunch/

I'm curious to see what other startups/groups have come up with. List your startup and a link to the lunch picker (if it's public).

64 comments

order
[+] stephenr|10 years ago|reply
This sounds like a uniquely American thing to me. I've never heard of this concept anywhere except California.

Everywhere I've worked on-site, if people wanted to eat together they just did that weird thing people do and talk to one another.

[+] jasonkester|10 years ago|reply
There's a delicate art to these negotiations if you want to end up going someplace good.

You can't just come out and say where you want to go, because it will get swatted down by everybody else who wants the Barbeque Joint or Sushi House or Rubio's Fish Tacos or Thai Garden. You have to let them wear each other down for a while until all the good options are off the table and everybody is resigning themselves to compromise on that lame soup place or Applebees or whatever.

Then you strike with Mama's Mexican Kitchen. Everybody will be so relieved that they don't have to eat another f'ng TGI Friday's meatloaf that they'll jump on the idea, even if they weren't in much of a Mexican mood 45 minutes ago when this stupid negotiation started.

[+] Rafert|10 years ago|reply
It's probably an extremely Dutch thing to do, but we have fresh bread delivered daily and sandwich filling in the fridge. On fridays some of us eat at various places near the office.
[+] Kalium|10 years ago|reply
Yeah... at my office this leads to endless amounts of bikeshedding, because the goal is consensus and everyone gets a veto. We would wind up at the same three spots every damn time.

I shortcut this by appointing myself lunch dictator.

[+] desas|10 years ago|reply
One place in the UK I worked at had something similar-ish - a breakfast butty ordering system. You designed your breakfast butty and pressed order, it would generate a spreadsheet at the of the day, for emailing to the cob shop. Someone would pick them up on the way to work the next day, distribute them and take the money.
[+] fosk|10 years ago|reply
I don't always feel like eating what other people want to eat, the problem here is finding every day some kind of food that everybody in the group wants to eat.

I always wanted to build an app that would track our preferences every day of the week, and then with machine learning predict what the team wants to eat on any given day.

[+] dvirsky|10 years ago|reply
I'm from Tel Aviv, and here we use a website (that's also a payed-for by the company credit card) to order our lunches.

Anyway they don't have an API, but we sniffed their AJAX stuff a bit and added some scripts to our Hubot that allow us to use Hipchat to order and get recommendations (including an I'm Feeling Lucky mode). We have company hackathons 3-4 times a year, and almost every hackathon had one project dedicated to hack the lunch ordering website.

BTW although they don't have an official API, some people here approached their team personally, and we got a bit of help in doing our unofficial hacks from them.

[+] lucaspiller|10 years ago|reply
How do you not get sick of being stuck in the office for 8+ hours a day? I like lunch as it gives me a break to go outside for a walk :)
[+] nness|10 years ago|reply
This seems like a problem that doesn't require such an over-engineered solution. But I suppose over-engineering social arrangements is the underlying proposition of many Silicon Valley ventures...
[+] nathancahill|10 years ago|reply
That, and the not invented here syndrome.
[+] dofishwatchtv|10 years ago|reply
We had the simplest "app" possible - cross platform, no Go or Rust or React. It was simply the newest member of the team had to go and collect the ordered lunches, organise the menus etc. Simple algo, simple implementation.
[+] chrismorgan|10 years ago|reply
“Hey, food intern! Go talk to people, ask them what they want; if they don’t react, tell ’em they’ll get dry bread and water on a rust-covered plate.”
[+] scrapcode|10 years ago|reply
This guy knows his computering.
[+] bigbento|10 years ago|reply
When I worked at OkCupid Labs, we normally just did daily lunch ad-hoc. However, we set up a little app that would organize a weekly lunch "date" where people would have a one-to-one with someone from a different team. I had some pretty interesting conversations come up from that, and if I were approaching this "problem", would start from there again.
[+] bayonetz|10 years ago|reply
Ours was to pick which restaurant we would actually go out to eat at that day. You'd think it would be easy to just pick a place, but no, everyday it was an ordeal.

To seed we it, picked a list of places and trimmed any that were vetoed by even a single person. Then with the remainder everybody got a a couple votes to cast for their favorites from the list. Then we made an actual physical Wheel of Fortune style wheel but with restaurants, each choice appearing as many times as it had been voted up in the seed list. It had about forty slots with the favorites appearing multiple times.

After making that, it was super fun to pick our lunch spot everyday by spinning this big wheel. It had the little plink plink spikes that the pointer brushed past and everything. Whoever had done a good deed that day got to be the "contestant", vying for our lunch fortunes.

Man, a novelty store should start selling customizable versions of these for offices...

[+] JasonH09|10 years ago|reply
I created an app for just my group of friends to pick where to go to eat.

It had tags for different places and would narrow the selection down and ultimately pick one. You could say where people in the group had been recently and they would be removed, say which area of the city you wanted, delivery, take-out, dine-in, fast food, and other properties. People also had profiles where they could choose restaurants they didn't like and when you went through the picking wizard, you would indicate who was going and it would discard any restaurants that those people disliked from the potential pool. A random number generator would then make the final decision from the possible options.

[+] DigitalSea|10 years ago|reply
The startup I contracted for didn't have an app. We would just take turns picking a place for everyone to eat at. One day I would pick a place, someone else would take us through some suspicious alley ways to a hidden Mexican place, etc.
[+] mikejchin|10 years ago|reply
We've been experimenting with voting systems in order to decide where to eat. We weren't sure which system was the fairest, so we built apps that used plurality, probabilistic, instant-runoff, and preferential voting. It reached the point where we were voting on which voting system to use!

The system we settled on was a modified Borda count (http://en.wikipedia.org/wiki/Borda_count#Modified_Borda_coun...). Our app isn't public, but I recommend this system, because it seems to have maximized happiness in our company!

[+] underyx|10 years ago|reply
Here's what we used at Allmyles: https://github.com/underyx/footlong

There's an Android app that lists the daily menus in Budapest, Hungary, where we're located. From there it was just a matter of finding the internal API of this app, and hooking it up to HipChat. We migrated to Slack and haven't yet got around to updating footlong to post the results there, though. I checked our HipChat yesterday and it was practically nothing but footlong posts.

[+] fittom|10 years ago|reply
In Berlin we have a small startup based on this idea. You can subscribe to our newsletter and we send you the daily menu of the restaurants in your area every day. With forwarding this e-mail to your colleagues, all of you can select the favourites using the up-vote buttons in the email. You can track the votes on the website, but you will receive a summary about the results as well. Give a try if you in Berlin: https://www.halb1.de/
[+] Joeri|10 years ago|reply
We sell a room and services reservation software, and have set it up so you can order lunch and have it delivered to the office, from a windows desktop client, from a browser, from outlook or from a mobile app. Billing happens automatically through the integrated contracts and billing system. It's somewhat overkill, but we consider it a form of dogfooding. The company is mcs.fm
[+] ajuc|10 years ago|reply
Yes, we had a part of our team learn salesforce API at the time, and we ordered dinner for most of the office every day, it was cumbersome to gather the orders and phone the few food seller every day, so the first app in salesforce they written was lunch ordering app. There were even stats with favorite dishes for everybody, and average money spent :)
[+] ggaughan|10 years ago|reply
I found it painful to watch people collect everyone's orders and then phone them in and then try to work out what was in the delivery bags and who owed what. So I built https://fuseorder.com/

(just add an event for each meal. You can add your own places and menus as needed)

[+] egeozcan|10 years ago|reply
I had created "The Lunch Planner". There's a barely-functional demo at:

http://providefoodfor.us/restaurants

It's on Bitbucket and I need to open-source it at some point. Built with Meteor. It was my "oh let's try this shiny new framework" project.

[+] nhdev|10 years ago|reply
I wrote http://www.collablunch.com/ for this purpose. The team uses it pretty regularly. And yes, way over engineered. I have it on my todo list to rewrite it in Meteor since a lot of the Web Socket code I wrote Meteor would have handle automatically.
[+] pawangupta11|10 years ago|reply
We experimented with a channel #Lunch on Slack, unfortunately it became a channel to share /giphy food
[+] edmack|10 years ago|reply
/giphy food is my FAVORITE slack usage!