I wanted to get some ideas on how a problem like this might be avoided. A mobile app (android, ios) that I work on uses a local sqllite DB to power an auto-suggest feature on the search screen. The idea is that since it's local (contains the most popular items in our database), it returns very fast and the user either sees the item they seek on the list, or press the search button, which invokes an API call to our server.
Now the problem is that I get feedback from users all the time saying that the app doesn't have the same results as the search on the website. Of course this isn't the case because both the site and the app use the same search API. I suspect that the users get confused and think that the auto-suggest is the entire search result and never actually press the search button.
So the question is this, what techniques can we use to hint to the user that pressing the actual search button will give them more results? I'm toying with the idea of adding an entry at the bottom of the auto-suggest box that says, "More ...", which will just trigger the search function.
Any thoughts would be appreciated :-) Thanks!