When searching, the current implementation is making too many requests to the geocoder, with the corresponding update of the results list, one for each request. You can see the effect in the first columns of screenshots.
To improve the UX in this part, my idea is to rethink the debounce implementation, applying it to the onTextChangeListener. This way the request itself will be done only after DEBOUNCE_TIME milliseconds has passed without changing the term of search.
ISSUE
No related issue
Description
When searching, the current implementation is making too many requests to the geocoder, with the corresponding update of the results list, one for each request. You can see the effect in the first columns of screenshots.
To improve the UX in this part, my idea is to rethink the debounce implementation, applying it to the
onTextChangeListener. This way the request itself will be done only afterDEBOUNCE_TIMEmilliseconds has passed without changing the term of search.Screenshots
Mandatory GIF