Food-based social discovery has been a white whale for consumer app builders since the early days of Foursquare check-ins and Yelp friend feeds. Nobody cracked it. The apps that tried either collapsed into restaurant review tools or got absorbed by platforms with bigger distribution budgets.
Tasteit, a Berlin-based startup, thinks it has the framing right this time.
The core idea is direct: a dish is your entry point into a social graph. You find something you want to eat, see who else wants it, and turn that shared appetite into an actual meal together. No profiles built around personality quizzes. No swiping on faces. Just the thing you’re already doing, which is looking at food on your phone and wanting to eat it with someone.
Founder Giorgi Urushadze, a Forbes 30 Under 30 alum and Creative Director based in Berlin, has been public about the reasoning behind the concept. According to his LinkedIn activity, the team built early traction spending nothing on paid acquisition. That’s a meaningful signal for a social product, where organic growth is either happening or it isn’t. You can’t buy your way into a habit loop.
The product launched at Pitch Berlin and got solid traction when it went live.
What Tasteit is arguing, essentially, is that food is the most underused social coordination mechanism we have. Think about how often you’ve eaten alone because the logistics of finding someone who wants the same thing felt harder than it was worth. The app tries to close that gap by making the dish itself the shared object, the thing two people can point at before they’ve even decided whether they like each other.
That’s a genuinely interesting design choice.
Most social apps build connection around identity. You present yourself, someone evaluates that presentation, and if the mutual evaluation clears some threshold, you get to talk. Tasteit inverts this. The food comes first. You’re not being evaluated. The ramen is being evaluated. You just happen to also want the ramen.
This matters more than it might sound because the identity-first model carries real friction. People perform. They optimize their profiles. They pick photos that don’t look like them at their worst. None of that is present when the shared object is a bowl of something you’re both hungry for.
The Berlin context is worth paying attention to. Germany’s startup scene has produced durable consumer products, and Berlin specifically has a food culture that functions as genuine social infrastructure. People there eat out in groups, discover new spots collaboratively, and treat meal decisions as community projects in a way that doesn’t fully translate to American cities where eating alone at a counter is practically aspirational. Tasteit’s home market may give it a cleaner initial use case than a San Francisco launch would have produced.
Urushadze’s background in creative direction also shows up in how the product is positioned. The language around Tasteit, phrases like “nobody owns food as a social behavior” and “food as the most natural reason to meet,” reads less like startup boilerplate and more like someone who spent time thinking about what the product actually means to people. Whether that translates into clean product execution is a separate question, but the conceptual clarity is there from the start.
The comparison that keeps surfacing when people talk about Tasteit is dating apps, and the team seems to lean into this rather than run from it. Urushadze has tagged posts with “#antidatingapp,” which tells you something about how they want to be perceived. The problem with dating apps is not that people don’t want to meet people. The problem is the framing. Being on a dating app means admitting you need one. Being on a food discovery app just means you like food, which is everybody.
This is smart positioning if they can hold it.
The risk is obvious. Social apps live or die on network density, and density takes time to build. The first 10,000 users of a food-based social graph are only useful if they’re in the same city, looking for the same kinds of food, and available at overlapping times. Matching someone in Mitte with someone in Prenzlauer Berg over a shared love of Georgian khachapuri is a better outcome than matching them with someone in Hamburg, but only if the app has enough users in both neighborhoods to make the match feel natural rather than desperate.
Tasteit’s product page describes the loop as: discover a dish, see who loves it, turn that into a real meal together. Three steps. That’s about right for a consumer social product. If you can’t describe the core loop in three steps, you haven’t figured it out yet.
The question is what happens after the meal. Every social product needs a reason to come back, and “you already ate together” is a past event, not a return trigger. Does the app prompt you to log what you ate? Do you follow each other and see each other’s future food discoveries? Does the shared meal become a node in a longer relationship graph, or is it a one-time transaction? The source material doesn’t answer this, and it’s the most important design question Tasteit needs to get right.
This is not a small product challenge. Instagram’s food content works because the utility is broadcasting, not coordinating. Yelp’s social features never really landed because Yelp is a review database first. What Tasteit is attempting is harder than either: real-time social coordination built around a perishable, time-sensitive shared interest. You’re not just matching people on taste. You’re matching them on taste, availability, location, and appetite, all at the same moment.
Four variables. Simultaneously. That’s a cold start problem that makes traditional social apps look manageable.
Urushadze told his LinkedIn followers he was “wrong about my startup,” referring to a shift in how he understood what Tasteit actually is. He didn’t elaborate publicly on the specifics of what changed, but founders who can identify when their original thesis was wrong and update accordingly tend to build better products than founders who defend the first version of everything. The fact that he posted about it publicly suggests some comfort with intellectual honesty, which is at least correlated with good product decisions.
The food tech category has seen enough failure modes that any new entrant deserves skepticism. Apps built around food discovery have generally either found a niche and stayed small, or scaled into something generic that lost the original insight. The National Restaurant Association has tracked declining solo dining occasions over the past three years, which points to a real behavioral shift that Tasteit’s premise addresses. People want to eat with other people. The gap is coordination, not desire.
If Tasteit can solve the coordination problem at city scale in Berlin, the model ports to any dense urban market with a real food culture. That’s a large addressable opportunity, larger than the product’s current form factor might suggest.
The 162 votes and 28 comments on launch day are a modest signal, not a mandate. Consumer social is brutal, and Berlin is not yet a product market that translates automatically to global scale. But the concept has internal logic, the founder appears to be paying attention to what’s actually true about the product, and the positioning avoids most of the traps that sink food-adjacent startups.
What Tasteit needs in the next 12 months is a single city where the density problem is solved well enough that the core loop works reliably. One neighborhood where you can open the app, find someone who wants the same dish, and eat with them within 48 hours. According to research from the MIT Media Lab on social coordination apps, products that achieve their core loop reliably in a single dense geography almost always find a path to expansion. Products that try to scale before achieving that local reliability almost never do.
Berlin is a reasonable place to try. The food culture is real, the population is young and app-native, and the startup community there has shown it can produce products that travel.
Whether Tasteit becomes the product it’s describing depends on execution details that aren’t visible yet from the outside, and on whether the founding team can hold the conceptual discipline of the original idea through the messy middle of building a social graph from nothing. The idea deserves the attempt.