Algolia Places provides a fast, distributed and easy way to use address search autocomplete JavaScript library on your website. It has been designed to improve the user experience of your HTML forms.
@holgersindbaek We've been promoting the JavaScript a lot, but the other API clients are coming. In the meantime, here is the documentation of the underlying REST API: https://community.algolia.com/pl...
@holgersindbaek No you cannot as-is; you'll need to use that new REST API endpoint. It's actually wrapping a few Algolia Search queries & custom logic for the Places use-case.
We'll soon release a blog post explaining how we built that, diving into technical details of the implementation.
This is amazing. I remember building an ad-hoc service in 2011 by patching multiple libraries and APIs, and it took us weeks to get it right.
This is so useful to reduce friction in shopping carts or signup forms!
This is a good start, but nowhere close to where I want it to be so it could fit my use case at Stay22.com (where we work mostly with Venues and POIs, and our autocomplete is already mixed with Algoia and Google Places using Bloohound from bootstrap)
Hey hunters!
As you may know, we love to experiment with our API and build new community services. We're super excited today to introduce Algolia Places, making it easy for developers to turn any HTML ‹input› into an autocomplete! We were able to build it thanks to the awesomeness of OpenStreetMap and Geonames. Compared to Google Places, it is highly customizable and can be enriched with additional data sources.
Check out the blog post (https://blog.algolia.com/introdu...) or directly try it for yourself!
@evanlodge@dessaigne Our current focus is all about UX: we want Algolia Places to be easily extended and customizable to be deeply integrated in your apps.
For instance. you can mix your own data & Places' suggestions in a single dropdown menu: https://community.algolia.com/pl...
You can also use it to auto-fill your boring forms: https://community.algolia.com/pl...
The underlying data is not yet at the level of what Google provides, but we're leveraging the progress that OpenStreetMap & GeoNames are making every day!
@evanlodge the picture might be bigger… let's just wait the moment when it'd be asked to algolia to elaborate on use cases compared to firebase (or likes)
I like the idea but it's going to need a lot of work before it's really usable for most serious applicataions. Simple example: type "USA" (it shows small towns in Eastern Europe) or type a zipcode, or type "England" (it defaults to London, and then England, Arkansas - it never shows England as an area). This isn't Aloglia's issue but the limitations of openstreetmap data. It's messy. While this works for most inputs - the tag-line "turn any input" would be misleading, at least right now until they have enough user data to improve it. I do like the idea and am glad it's been worked on.
@chris_colleran We rely on the OpenStreetMap & GeoNames data which may have a few missing places. Would be awesome if you could submit the "irrelevant/missing result" form here Chris: https://community.algolia.com/pl... much appreciated :)
@eeus You can integrate your own custom suggestions in a single dropdown menu, this is definitely the way to go. Check out our autocomplete.js integration: https://community.algolia.com/pl...
@sylvainutard In zip codes for The Netherlands only 4 numbers are showed, the 2 letters that come afterwards are missing. This should be the format: 1234XY. Rest looks fine and accurate, small places as well. Lightning fast. 👍
Online Solitaire