Scene Kya Hai?
An outing app for people who cannot decide where to go.
Hundreds of places, a never-ending scroll, and the plan falls apart before anyone leaves the house. So stop offering a list and give one answer.
Scene Kya Hai?
An outing app for people who cannot decide where to go.
Read the full case study on Behance↗THE FULL DECK · RESEARCH, FLOW AND VISUAL DESIGNTHE BETHundreds of places, a never-ending scroll, and the plan falls apart before anyone leaves the house. So stop offering a list and give one answer.
An outing app for people who cannot decide. Food, fun or somewhere to sit for three hours, it locks in a plan without the usual back and forth. You pick a vibe, answer three short questions, and it returns one place instead of a list.
End the search rather than extend it. Replace an endless scroll of options with a single suggestion a person can accept, or shuffle away, in one tap.
Product design. Problem framing, flow, interface and the visual system.
Figma
An outing app for people who cannot decide. Food, fun or somewhere to sit for three hours, it locks in a plan without the usual back and forth. You pick a vibe, answer three short questions, and it returns one place instead of a list.
End the search rather than extend it. Replace an endless scroll of options with a single suggestion a person can accept, or shuffle away, in one tap.
Product design. Problem framing, flow, interface and the visual system.
Figma
Too many choices, no clear answer.
The scroll never ends
Hundreds of places sit one search away. That sounds like abundance and behaves like paralysis. The more options load, the less likely anyone is to pick one.
Groups do not decide
Every plan runs through a chat where nobody wants to choose on everyone else’s behalf, so the suggestion loop keeps going until the evening is gone.
Discovery apps reward browsing
Listings, ratings and filters are built to keep you looking. None of them are built to end the search, which is the only thing a person wants at that moment.
Before you know it the plan is off. The product is not discovery. It is the full stop.
01
Ask for a vibe, not a category.
Every discovery app opens with cuisine, price and distance, which are the filters a database wants rather than the words a person uses. Scene opens by asking how you want the evening to feel. Adventurous, cosy, budget-friendly, lively. Those become the keywords the matching runs on, so the input is something you can answer without thinking.
02
Three questions, then stop asking.
Who is coming, how many of you, and when. That is the whole brief. Each extra question improves the match slightly and costs far more than it returns, because a person who wanted to avoid deciding has just been handed a form. Three was the point where the answer got good enough to stop.
03
One answer, and a shuffle.
The result screen shows a single place, with distance, opening hours and what it is good for. There is no list and no ranking to second-guess. The only two moves are Visit or Shuffle, so the decision is either made or handed back to the app, and either way it ends.
The vibe words are the query.
Keywords, not filters
The vibe words picked at sign-up, or inside a finder request, are stored as keywords rather than as category filters. The thing a person can answer becomes the thing the system searches on.
Matched against the map
Those keywords go to the Google Maps API, which returns real places nearby that actually carry them, so the shortlist is grounded in what is open and close rather than in what is sponsored.
A handful, then one
The app returns a short set from the keywords entered, and the interface shows them one at a time. The narrowing happens in the database so it never has to happen in the interface.
Define, design, validate, repeated. The prototype was tested on the ground with the people it was built for rather than in a room.
So sit back, relax, and let us figure out the scene.
One question, three answers and a single suggestion. Everything else was cut because it gave the user another chance to keep looking.