Search in applications
Most people walk past the homeless. They ignore the out-thrust hands, the pleas for ‘spare change’, and avoid the possibility of making eye contact. Search is the homeless guy or gal of your App.
You’ve built all of these elaborate features and imagined use cases, but the basic route for a user to discover what data is inside your App, that meets their needs, is ignored and left to languish on the cold street. It’s an afterthought.
At most, you’ve implemented a text box that does a basic fuzzy string matching and lands the user on a useless list page of results, hopefully with some paging controls. At best, you’ve done the basics and provided some sort of ordering maybe. Your App sucks at search. It sucks in every way that is meaningful to the user.
Users should not have to think about what type of object they want to search for in your App (‘Is it a contact, an address, a postcode?’), and choose that thing from a dropdown before the search works correctly. The search results should not be a list of context-less results that require further analysis by the user. Results should not share the same cookie-cutter visual appearance: if some results are more relevant than others, make them visually more relevant!
Every time you build an App that has useless search, you’re denting and diminishing the value that your App provides to the user.
It’s said that Security can’t be baked into an application at the end, that it’s got to be a primary concern. Well, just like Security, neither can a good and useful Search feature.
So start at the beginning, planning out how users will search the data they’ve put into your application, what tasks will they try to solve by searching, and bake it into the cake from the start. Spare your search feature some change.
Your users will thank you, and find your App to be much more useful - I guarantee it.