News for hackers. Stuff that matters.
Re:What software engineers should know about search (2017) by formerly_proven on Monday October 18, 2021 @08:27AM (#28904685)
> Either search is not an important feature, and a suboptimal, DIY implementation that looks OK is good enough. Or, search is a primary feature and then you need control over it. IE, if you have an online store, travel site or dating app with a search based UI, then you'll probably roll your own.

Most stores have garbage search and even worse filtering. >98 % of stores have only categories for filtering and only trash like "price" for sorting. In the 2 % of stores that can actually do faceted search the number of facets is too small (e.g. shoe stores which only have a "size" facet plus categories) or the data in the facets is garbage. This is likely a big contributor to sites like Geizhals existing, whose sole purpose is to offer decent search and filtering.

Re:What software engineers should know about search (2017) by wongarsu on Monday October 18, 2021 @09:30AM (#28905244)
Ninety percent of ecommerce sites have terrible search because ninety percent of everything is crap [1].

That doesn't mean that having a great search can't help your shop get repeat customers, just like good service, fast shipping or a good checkout flow can.

1: https://en.wikipedia.org/wiki/Sturgeon%27s_law

Re:What software engineers should know about search (2017) by netcan on Monday October 18, 2021 @08:54AM (#28904910)
I don't disagree.

If you have bad search, and search is a primary feature, then your ux sucks. I just don't think "just use google" is a viable alternative to making search good.

If you're making an online store, search is probably important, and a major determinant of how well the software works. The best way to handle that is with search that doesn't suck. It may be hard, but that's the job. Fair point that search is not trivial to do well, but that doesn't mean it isn't the job.