Speaking as co-founder of Geocode Earth(https://geocode.earth) where we do provide autocomplete geocoding, it's a much, _much_ harder problem than regular geocoding (not that any geocoding is exactly...easy).
For one, the latency requirements are much more strict. People type fast and if results don't come in within about 100ms or so, the interface doesn't feel responsive. We spend a ton of time ensuring our servers are as fast as possible. There's always more work to do here, since obviously network latency matters, so where your servers are matters too.
Second, the queries themselves are much harder. If someone has typed "India", did they want the country? Or have they not yet finished typing Indiana? The answer probably depends on their location, which may not always be available. That's a simple example, obviously there are much more subtle queries that don't always have as clear an answer.
Anyways, we enjoy the challenge of autocomplete and hope to continue to do a better and better job, even after Amazon inevitably releases their own :)
For one, the latency requirements are much more strict. People type fast and if results don't come in within about 100ms or so, the interface doesn't feel responsive. We spend a ton of time ensuring our servers are as fast as possible. There's always more work to do here, since obviously network latency matters, so where your servers are matters too.
Second, the queries themselves are much harder. If someone has typed "India", did they want the country? Or have they not yet finished typing Indiana? The answer probably depends on their location, which may not always be available. That's a simple example, obviously there are much more subtle queries that don't always have as clear an answer.
Anyways, we enjoy the challenge of autocomplete and hope to continue to do a better and better job, even after Amazon inevitably releases their own :)