Search is not just a feature, it’s an epic.
We use things subconsciously without thinking about the woolly mammoth fighting T-Rexs in the background— until you have to implement it. Search seemed to be the simplest feature that could be done with a single line of code; well, unfortunately this is not that accurate.
“Enjoy the little things, for one day you may look back and realize they were the big things.” ~Robert Brault
People usually use the mobile app to find certain info. They should be able to quickly locate content by searching.;
What we are going to demonstrate is the search functionality as we thought while designing an ERP system.
What we know:
- ERP system is based on huge dataset.
- Data are dynamic and different per role.
- Users mostly forget item’s code.
As for the ERP, A growing desire to access data anywhere and everywhere. For the customer, it is an opportunity to eliminate the gap and streamline processes in real-time.
For example, I would like to get “Invoices for customer -HP- that have payment due tomorrow” The ability to perform tasks like “signing contracts” on phones. Doing such a task should be as smooth and responsive as possible.
Basic Search Scenario:
1- Locate search bar
2- Type keyword(s)
3- Get results.
Designing For An Explicit Pattern
We choose “Explicit Search” pattern as it relies on explicit user action to perform search.
That action might be to tap a search button on the screen, and write the keywords that you want to search for. The results are displayed in the area below the search bar.
Our own target is to make it proactive and smart enough to find a query using minimal user input with responsive results.
We also want it to be persistent at home screen inspired by Chimamanda’s quote.
“I think you travel to search and you come back home to find yourself there.” ― Chimamanda Ngozi
Sometimes it is easier (and faster) to get to the desired result by scoping the search criteria before performing the search. ERP app supports large amounts of information, it would be difficult and slower to search in all tables and get accurate results.
So, going to “Scoped Search” pattern with explicit search will help us get the desired result.
Example:
User wants to get “Invoice # 48082 “, so it will be faster to give him the option to not hit all DB records. So, user will select “Accounting”or “Invoices module”then write down his search keywords into search box.
Going with Auto-complete
As the user enters a query, the search suggestions shift to “auto-complete” pattern. As the user types, the suggestions are filtered and sorted.
What sticks with our minds is how far we would enhance the search experience.
Then, in the same heartbeat would say something like, “ERP systems are huge and finding a query is almost like finding a nemo in sydney.” Were we all trying to be so unique that we ended up amalgamating into one?
Based on Kano model we just achieved the basic functionality, we do understand that the execution is playing a game changer role to the overall experience. Also performance with keeping mobile processing power/battery life in mind.
We didn’t forget those simple states:
- First time search
- No match result
Here’s the final output:
I’m really thankful for Abeer my co-founder, for her incredibly detailed and great efforts to help us build such useful resources and get things done.
At Tremoloo, we used to craft whole experience starting from component micro-interactions to complete epic pages.
Find out more about us on www.tremoloo.com
