1/ At #Neeva, design is the act of giving form to an idea: we gather data and inspiration, think, make, and iterate through feedback. 💡
Here's how our team, working alongside the ✨Neeva Community✨, shaped our latest news tool, #BiasBuster...
(read on 📖)
2/ To improve the news experience on Neeva, we solicited insights from users of various news outlets.
One early finding 👉 the journey to get daily news typically started from news providers' sites and apps, but NOT from a search engine.
🤔
3/ So we asked ourselves, when does a search engine becomes necessary and helpful in the journey? 💭
Several users shared that they searched for specific events and stories about which they wanted to learn more.
An avid news user put, "Search is for focused topics.".
4/ The users visited their typical news providers' services to get daily news. But where did they go to get more points of view, especially for political news?
Some said their news sources were sufficient. ✔️
Some went out to check opposing views from the sources they knew. 👀
5/ Checking POVs by visiting multiple outlets takes a LOT of effort.
But do you know who’s capable of making this process effortless? Neeva! 🦸
We pursued the idea. 🧠
6/ Limited sources and freshness were common complaints about news on search engines. Quick retrieval of POVs from broad & fresh sources was also crucial.
The critical aspects of our backend and frontend to rally around were:
✨Broad✨
✨Fresh✨
✨Fast✨
✨Easy✨
7/ Going into detail design development, we generated ideas to express that this tool was about finding and viewing news articles in the spectrum.
Here are ideas we came up with ⬇️
8/ We struggled to find ways to signal and invite the user to drag the control around to set the desired position. 😑
Our caring Neeva Makers community unblocked us with detailed feedback.
Thank you Makers for helping us all along throughout the process! 💓
9/ We investigated UI motions to visually explain news source changes. Also, the motion exercise using the @Framer Motion, an animation library, answered our pathway for UI implementation.
10/ We chose the seesaw figure with color gradients.
We rotated the half-circle within a rectangular container as a mask because it was:
✅ Sufficient enough to express the POV selection
✅ Practical to implement
We prototyped in @principleapp + gathered usability issues.
11/ When an end-to-end build was ready, 80+ opted-in users shared candid critiques.
This sped up the backend improvements & UI polishes:
📌 Wider handle
📌 Clarity on what range is selected
📌 Hover tilt in a randomized direction
📌 Handle dot color changes for a bit of fun
12/ After many meetings, @clickup tickets, and a lot of math, we refined other details, like snapping the thumb to the nearest point on the spectrum and rubber-banding on the edges.
And we shipped in the US just in time for the midterm elections in November. 🙌
13/ What's next? Users shared:
🗣️ Bias Buster can help them relate better to their friends' perspectives
🗣️ Neeva should build an AI summary of opinions
So, the fun of making a better news experience will continue... 😄
1/ It's not the size, it's the skill - now releasing #Neeva's Query Embedding Model!
Our query embedding model beats @openai’s Curie which is orders of magnitude bigger and 100000x more expensive. 🤯
Keep reading to find out how... 📖
2/ Query understanding is the life blood of #searchengines. Large search engines spent millions of SWE hours building various signals like synonymy, spelling, term weighting, compounds, etc.
3/ We solve the problem of #query similarity: when 2 user queries looking for the same information on the web.
Why is this useful? Query-click data for web docs = strongest signal for search, QA, etc.; solving query equivalence => smear click signal over lots of user queries
1/ Google will do just about anything to maintain its monopoly power
Fear-inducing pop-ups with misleading designs to trick users into going back to Google search ✅
What’s a competing search engine to do? The only thing we can…Design and innovate our way out of it! 🧵
2/ By default, Google Chrome comes with Google search – no surprise there.
However, if a user prefers a more privacy focused search engine, they have to jump through a few hoops to install an extension and make it as the default.
All in all not terribly difficult so far, but…
3/ The last thing Google wants is to lose a user, especially from their cash cow – search.
So, under the guise of security, upon installing a new search extension such as Neeva and attempting your first search from the omnibar, they deploy the misleading warning prompt.
1/ When someone types “neeva” into search, how do we know they mean “neeva.com” instead of “neevaneevaneeva.com”? After all, the second has 3 times as much neeva!
See how you can do much better than vanilla TF-IDF / cosine similarity for textual relevance!🧵
2/ Textual relevance is only one part of document ranking (alongside signals like centrality, page quality, and click rate)
But it’s one the most important parts and the one we’ll be covering in today’s thread.
3/ The most popular way to rank documents relative to queries is to use TF-IDF vector representation.
Essentially, this claims the more often a term occurs on a page (TF), and the less often it occurs on other pages (IDF) the more likely that term is to be relevant to the page.