I\'ve got a SearchView
setup, and I have a loosely decoupled architecture using Retrofit
and Otto
.
I am wondering what the
So to answer this question in a sufficient way, as I was not satisfied with the other answers here there are a few more steps to consider in this problem.
First we would need to ask a few questions in regards to how we would tackle this issue:
And many more questions.
I would probably first build a custom adapter to handle the querying in the search, then implement aggressive caching on the user's queries. This is important in the sense that a user's queries are very important. It would probably make sense to only used cached results for Autocomplete
it is very expensive to implement autocomplete and have it ping the server at every text change.
Caching can be accomplished by using the SQLite
helpers in Android. This can be expensive, but we are dealing with simple query objects, (as this should be the case from the API the objects should be memory or byte size expensive).
I think there is no sense to make an API call before user stopped typing. So, you can put a delay, say, 500ms. When user stops typing, after 500ms you make an API call and show the results.
You can use a Handler
's postDelayed
method for scheduling search API calls. You can use Handler to control the message queue. You post a delayed Runnable
each time user types a character and cancel previous messages. It will look this way:
public void onTextChanged(CharSequence s, int start, int before, int count) {
handler.removeCallbacks(searchRunnable);
handler.postDelayed(searchRunnable, 500);
}