Most review apps are built for strangers. The ratings average out to a four, everyone’s optimising for visibility, and you still don’t know whether you’ll like the place.
Bytly is the opposite bet: reviews that only your friends see. A small, closed graph where the signal is high because the people in it actually know your taste.
What I own
Two developers. My collaborator handles backend architecture, system setup, and core infrastructure; I handle product direction, UI, and general app development.
The map is the interface
Discovery is a map rather than a list, with restaurant detail and turn-by-turn navigation layered on top. Food discovery is inherently spatial — you don’t want the best restaurant, you want the best restaurant near where you’re standing.
Markers are typed, so the map answers two questions at once: where the food is, and whose opinion is attached to it. A friend’s review, something on your own list, and a place neither of you has tried are three different things, and they don’t look alike. You can switch any of those layers off when the map gets busy.
Reviews people will actually finish
The review form is a wizard, and the split is deliberate. The first page is the whole review if you want it to be: a rating, what it cost, one line of what you thought. Everything after it — quick reactions, who you were with and what you ordered, photos — is optional depth.
A form that demands a paragraph gets abandoned in the car park, and the reviews that survive that kind of form are the ones written by people with something to prove. Making the fast path complete is what keeps ordinary meals in the app.
Tags that argue with themselves
Cuisine labels come out of place data first, but that data is generic — half of everything is tagged “Restaurant” or “Food”, which tells you nothing. So those get filtered out, users can add their own tags, and everyone votes. Net votes decide what a place is actually known for.
It’s the one part of the app where the closed friend graph opens up: taste is private, but whether somewhere is a ramen place is not.
Collections
Saved spots go into named collections — “Date Night”, “Coffee Runs”, “Must-Try Ramen” — each with its own icon.
The wishlist turned out to matter more than expected. Reviews only get written after you’ve eaten somewhere, so an app made of reviews alone has nothing to say until you’re already out. The wishlist is what gives it a reason to be opened on a Tuesday afternoon.
Privacy as the product, not a setting
Reviews are friends-only by default and can be opened up per review, not per account. Friends are added by username rather than by scraping contacts. Blocking someone removes the friendship with it, and an account can be deleted from inside the app without emailing anyone.
None of that is a compliance checklist — a closed graph is only worth anything if people believe it’s closed, and honest reviews are the entire product.
Where it is now
Built with React Native and Expo on top of Supabase, iOS first, with updates shipped over the air between store builds. It’s currently being prepared for its first public App Store release.