Imagine you are standing in the centre of Lisbon at 7am. You have just arrived, the hotel room is not ready yet, and you want to know: what should I do right now? You open a travel app and search for "things to do in Lisbon." The top result is a fado show in the Alfama district. The second is a sunset cruise on the Tagus. The third is a Michelin-starred restaurant.
None of these are useful at 7am. The fado show starts at 9pm. The sunset cruise departs at 6:30pm. The restaurant opens for dinner only. What you actually need is a cafe that is open now, within walking distance, that serves good coffee and a pastel de nata. But no travel app will tell you that, because most travel apps do not know what time it is. Or rather, they know -- they just do not care.
The travel industry has spent two decades building recommendation systems based on a simple premise: find out what people liked, rank it, and show the highest-ranked options first. This is the logic behind TripAdvisor ratings, Google Maps star scores, and every "Top 10" listicle ever written. And for pre-trip planning, it works reasonably well. If you are deciding which city to visit next month, aggregate ratings are genuinely helpful.
But in the moment -- when you are actually there, standing on an actual street, with actual hunger or boredom or curiosity -- aggregate ratings fail spectacularly. They fail because they strip away context. A 4.8-star restaurant is objectively excellent, but if it does not open for another four hours, that number is meaningless to you right now.
This is not a new observation. Researchers at the MIT Media Lab have been studying contextual recommendation systems since the early 2010s, and a 2022 paper from the University of Trento found that traveller satisfaction with recommendations increased by 35-40% when those recommendations were filtered by temporal relevance -- in plain language, when they showed things that were actually available at the time the person was looking.
That sounds obvious. It is obvious. And yet most travel apps still do not do it.
Consider how radically different your needs are at different times of day, using a single city as an example. In Barcelona:
You want coffee and breakfast. Possibly a morning walk. The beach is quiet. The major museums are closed. La Boqueria market opens at 8am and is worth arriving early before the tour groups. The most useful recommendation at this hour is a bakery or cafe within walking distance of wherever you are staying, one that is already open and not a 30-minute walk away.
Museums are open. Walking tours are starting. The temperature is comfortable for sightseeing. This is when "top attractions" lists become relevant. A recommendation for the Picasso Museum or a guided Gothic Quarter walk makes sense now, whereas it would have been useless four hours earlier.
In Barcelona, this is lunch time. Not noon, as many tourists assume, but 2pm. The restaurants that locals eat at are filling up now. If it is July, the heat is at its peak, and an indoor activity or a shaded lunch terrace is far more appealing than a walking tour. The weather is no longer a background detail; it is actively shaping what you should do.
The heat is fading. This is the best time for a walk along the waterfront or through the Eixample district. Rooftop bars are opening. The light is perfect for photography. Recommendations should shift toward outdoor activities, aperitivo bars, and the kind of aimless wandering that makes travel memorable.
Dinner time in Spain. The restaurants that were empty at 7pm are now full of locals. Flamenco shows are about to start. The Gothic Quarter comes alive. The recommendations you need now are completely different from what you needed at 7am, even though you are in the same city, possibly on the same street.
Weather is arguably the most ignored factor in travel recommendations, which is strange because it is one of the most powerful determinants of what you should actually do.
According to a 2024 study published in Tourism Management, weather was the primary reason for itinerary changes on 43% of travel days surveyed. Nearly half the time, what travellers planned to do was altered by what the weather allowed them to do. And yet virtually no travel recommendation platform incorporates real-time weather into its suggestions.
The practical impact is significant. On a rainy day in Rome, the Colosseum is miserable. The Vatican Museums, which are entirely indoors, are ideal. A rooftop restaurant is a disaster; a cosy trattoria in Trastevere is perfect. But if you search "things to do in Rome" on any major platform, the results are identical whether it is 35 degrees and sunny or 8 degrees and pouring rain.
Weather also affects less obvious things. A food market is wonderful on a cool morning and unbearable in 38-degree heat. A boat tour is delightful in calm conditions and nauseating in choppy seas. An outdoor escape room is fun in spring and miserable in a downpour. These are not edge cases; they are the reality of travel for roughly half of all travel days.
The third contextual factor that most recommendation systems handle poorly is distance. Not distance in kilometres, which every map app can calculate, but practical distance -- how far something actually feels given your current situation.
A museum that is 2 kilometres away feels very different depending on whether it is a pleasant 20-minute walk on a cool morning or a sweaty 25-minute trudge in afternoon heat. A restaurant that is a 5-minute walk away is infinitely more appealing at 9pm when you are tired than a slightly better restaurant that requires a 15-minute taxi ride.
Research from the World Tourism Organisation (UNWTO) suggests that tourists in urban environments rarely travel more than 1.5 kilometres from their current location for a spontaneous activity. For planned activities, the radius extends to about 5 kilometres. For "what should I do right now?" decisions, the practical radius is often just a few hundred metres.
This means that a contextually relevant recommendation should weight proximity heavily. The third-best cafe within 200 metres is more useful than the best cafe 2 kilometres away, at least for the spontaneous, in-the-moment decisions that travellers make dozens of times per day.
If context is so obviously important, why do most travel apps ignore it? There are a few reasons.
First, static lists are easier to build and maintain. A "Top 10 Restaurants in Paris" list can be written once, updated quarterly, and will generate search traffic for years. A context-aware system that changes its recommendations every hour requires real-time data, continuous processing, and an entirely different design philosophy.
Second, the business model of most travel platforms is advertising and commission. TripAdvisor, Google Maps, and Yelp all generate revenue from businesses that pay for visibility. A system that shows you only what is relevant right now would show fewer results, which means fewer opportunities to display paid placements. The incentive to show you everything, rather than only what is useful, is financial.
Third, context-aware recommendation is genuinely harder than static ranking. It requires combining multiple data sources -- venue databases, opening hours, real-time weather, your GPS location -- and synthesising them into a single, coherent set of recommendations. Most travel apps were not built to do this. They were built to search and sort, which is a fundamentally different task from "understand what this person needs right now."
A context-aware travel discovery system would work fundamentally differently from what exists today. Instead of starting with a search query, it would start with your situation: where you are, what time it is, what the weather is like, and what you might be looking for. The results would change continuously as your context changes.
At 7am, it would show you cafes and bakeries that are open now, within walking distance. At noon, it would surface lunch options appropriate for the time and weather, filtering out the fine dining restaurants that only open for dinner. On a rainy afternoon, it would prioritise indoor activities: museums, galleries, cinemas, covered markets. At sunset, it would highlight rooftop bars and waterfront restaurants with west-facing views.
This is the approach that PingNear takes. It combines venue data, real-time weather, time of day, and your proximity to answer the question "what should I do right now, right here?" rather than "what is highest-rated in this city?" It is a fundamentally different question, and it requires a fundamentally different kind of app to answer it.
Even without a context-aware app, you can apply contextual thinking to improve your travel discovery right now:
The next generation of travel apps will not ask you to search. They will not show you a list of 500 restaurants sorted by rating. They will understand that you are a specific person in a specific place at a specific time with specific needs, and they will show you the handful of options that actually make sense right now.
This is not futuristic thinking. The data already exists: venue databases, opening hours, weather forecasts, GPS coordinates. The shift is in how that data is combined and presented. Instead of "here is everything, you figure it out," the approach becomes "here is what matters right now."
For travellers, this means less time scrolling through irrelevant results and more time doing the thing you actually came to do: experiencing a place. And that, ultimately, is what a good travel app should enable. Not more information, but more relevant information. Not more choices, but better choices. Not "what is best?" but "what is best for me, right now, right here?"