Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address the differences in Search and Nearby #261

Open
rinigus opened this issue Jun 2, 2019 · 2 comments
Open

Address the differences in Search and Nearby #261

rinigus opened this issue Jun 2, 2019 · 2 comments

Comments

@rinigus
Copy link
Owner

rinigus commented Jun 2, 2019

It seems to cause confusion on when to use Nearby and when Search. In HERE, looks like you can start typing a type of something (restaurant) and this will be shown as a first result. To distinguish, its shown in "" marks. Maybe something similar can be done in Pure Maps.

For example, if a type is selected, then we can ask for distance or even assume some distance and let users change it if needed.

Challenge will be to make such list while having multiple Nearby backends supported. Some may not even provide the list of types, I think.

Related issue is #101 which should allow to search by name of the restaurants, for example, and show the local ones first.

If merging two searches is too complicated, consider somehow making it clear which one to choose.

@rinigus
Copy link
Owner Author

rinigus commented Jul 12, 2020

We could make a list of all possible POI types and bundle it with the app. When user starts typing "cafe", search for POIs with cafe in the name, but also add an item in the list allowing to switch over to nearby search.

@rinigus
Copy link
Owner Author

rinigus commented Nov 5, 2021

An example of how can that be mixed well is HERE geocoder. Use the similar approach for such more clever geocoders and merge Nearby/Search under Search

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant