Before we deep dive into more features that make Zomato Search your favourite friend – the one who always listens and is there for you for all your (food) queries, a quick recap of what we discussed earlier –
Search is a great responsibility that we have built with care and attention to detail. Well we do power millions of search queries daily and as we said earlier, with great numbers, comes great responsibility.
So let’s dig into more features that make our rather your Search, better and customer-friendly.
What is it?
We introduced voice search to enable customers to explore restaurants, dishes, or cuisines through voice inputs. A customer can now tap the mic icon to activate the listening mode. The voice search processes the voice input into a text and displays the relevant results on the Search screen.
Why did we build it?
How did we build it?
To enable voice search, we deployed a variety of technical capabilities such as voice transcription (powered by Google on Android and speech framework on iOS devices) and the Natural Language Understanding, built in-house by the Engineering and Data Sciences teams.
How it works
What is it?
Natural Language Search allows customers to speak or type using their everyday language, rather than common keywords. Now customers can use slangs, phrases or partial sentences in their native language, just like in a casual conversation. While all along, the system in the backend transforms these sentences into searchable queries.
A few examples of Natural Language Search:
How did we build it?
We have built a model that can predict if a given sentence is a combination of a dish-dish (chai and samosa) or a dish-restaurant (chai from XYZ place). And once we identify these entities, we provide relevant results like the normal search.
This is one of the first yet pivotal steps in the direction of Natural Language search wherein we solve for some common use cases, such as:
Please note: XYZ is a blanket term used instead of specific restaurant names.
Do note: There will still be cases where we will not be able to gauge the intent of certain natural language searches.
What is it?
We added and merged regional names of dishes along with their global names. So customers can use either of the names and will get the relevant search results. For instance, search for Upit or Upma and all results for Upma will show up or search for Payasa and Kheer and you will see all results for Kheer.
Why did we build it?
For example, if a certain outlet has mentioned its dish name as Upit on the menu (regional dish name for the global counterpart Upma), the outlet will not be searchable for Upma. Similarly, while searching for Upit, outlets serving Upma would not show up in the old search ecosystem.
How did we build it?
In the screenshot attached, the regional alias is being shown with the global counterpart name in brackets.
Through our features, we made it easier for our customers to locate the dishes, cuisines, or restaurants. Our improvements also helped in reaching new customers, and overall made search easier and faster for everyone.
That’s all folks! On to the next problem solving.
This is a two-part series on how and why we introduced new ‘Search’ features on our app. If you are interested in solving similar problems with a customer-first eye and building features that impact millions, then connect with Himanshu Shukla on LinkedIn. We are always looking for builders at Zomato.
This blog was written by Himanshu Shukla and Saurav Singh in collaboration with Sandeep Veethu, Sonal Garg, Srinjay Kumar, and Shivansh Tamrakar.
All images/ videos are designed in-house.
-x-
Sources: