Here's another such idea (based on finding answers)...
____
A clean, dead-simple search engine that connects to information from Q&A data about the city you're in. So it's a Q&A site (again, with comment voting) regarding tourist-type questions and answers. The user can ask a new question ahead of their trip and hope for answers but the real use case is where the Q&A database is extensive enough that most questions are asked and answered already.
Ex. - Enter the Paris section. Type in the search field "hours Louvre" and the first and best answer would be the opening and closing times of the famous museum. No other clutter on the page.
Ex. 2 - If GPS-enabled, type in "bus Louvre" and it'd bring up the most relevant answer. "Take the 765. Every 30 min. Next one at 9am."
Short, sweet and simple. Only thing is, it'd need a Wikipedia-style editor allowing for corrections when answer is no longer current.
[1] https://news.ycombinator.com/item?id=7617048
Here's another such idea (based on finding answers)...
____
A clean, dead-simple search engine that connects to information from Q&A data about the city you're in. So it's a Q&A site (again, with comment voting) regarding tourist-type questions and answers. The user can ask a new question ahead of their trip and hope for answers but the real use case is where the Q&A database is extensive enough that most questions are asked and answered already.
Ex. - Enter the Paris section. Type in the search field "hours Louvre" and the first and best answer would be the opening and closing times of the famous museum. No other clutter on the page.
Ex. 2 - If GPS-enabled, type in "bus Louvre" and it'd bring up the most relevant answer. "Take the 765. Every 30 min. Next one at 9am."
Short, sweet and simple. Only thing is, it'd need a Wikipedia-style editor allowing for corrections when answer is no longer current.