3 ms·
This is really good. I would love to integrate this as an extension into our mobile browser. Hope that’s ok. https://insightbrowser.com/collections/cooking htt
by abhinavsharma 6y ago
This is really good. I would love to integrate this as an extension into our mobile browser. Hope that’s ok.
https://insightbrowser.com/collections/cooking https://insightbrowser.com/collections/cooking
Also I wanted to mention that the most important piece of metadata we’ve learnt about that users care about after ingredients is the website it’s sourced from. It’d be great to have that
- jabo 6y agoI actually sourced the aggregate dataset from this other Show HN earlier today: https://news.ycombinator.com/item?id=25356156 https://news.ycombinator.com/item?id=25356156 I do include the source website in the search results. It's the little icon on the bottom right of the search result card and it's also linked from the modal that opens up if you click on "Read cooking directions".
- abhinavsharma 6y agoOh cool I think you may have just hit the API limit for favicons if you use one from the HN traffic https://share.icloud.com/photos/0XKxqxHuzZV-7sO2wOx0y53YQ https://share.icloud.com/photos/0XKxqxHuzZV-7sO2wOx0y53YQ
- jabo 6y agoThat's actually the icon I intended to show! :) It's an icon of a ticket that gets printed in restaurant kitchens.
- abhinavsharma 6y agoI see, that’s cool but I was referencing something different — That it was important for users to quickly recognize the publisher on the search result page itself. They develop more trust with some sources than others. I wasn’t able to discern that. But if your goal is to showcase search capabilities to developers instead of a daily driver search engine it wouldn’t matter much.