A collection of saved places is often treated as a map problem. The harder product problem may be choosing between those places when a real situation arrives.
“Where can we get coffee near the station before the train?” includes location, purpose, and a time constraint. A saved pin without any context answers only one part of that question.
Keep place data and personal context separate
For a first design, I would use two conceptual records. The place record holds its name, location, and source. The save record holds who saved it, their note, and their intended use.
That separation matters because several people can save the same café for different reasons. One wants a working spot; another wants somewhere to meet a friend. Neither note needs to become a universal claim about the venue.
Let uncertain details remain uncertain
Personal notes such as “looked quiet in the video” should remain visibly personal. They should not turn into a verified amenity like “quiet workspace.” Likewise, an old save is not proof of current opening hours.
Show the source and provide a way to recheck details when someone is making a plan. A tool can preserve an idea without pretending every detail is current.
Design the result card around the decision
A compact card could display the place name, the user's reason for saving it, and its source. Filters might reflect practical questions: city, intended activity, or a person associated with the plan. Start with filters users actually ask for rather than an elaborate taxonomy.
Evaluate with a scenario
Give someone a collection of ten saved places and a specific plan: a short visit, a coffee meeting, or a weekend walk. Watch what information they need to choose confidently.
The design goal is to move from “I remember saving somewhere” to an informed next step. That connection between a save and its purpose is a recurring Némos theme.
Top comments (0)