6 ms·
Hey jnsie, sorry for the poor experience. I'm still working on the product and it definitely is in development mode. Although this sounds unintended, this is cu
by devanflores 5y ago
Hey jnsie, sorry for the poor experience. I'm still working on the product and it definitely is in development mode. Although this sounds unintended, this is currently how the recipe search algorithm works. Because the recipe does not include the ingredient "chicken breast", no results come up. However, multiple recipes include the ingredient "chicken", which lead to you getting a result. I'm working on developing some kind of smart detection algorithm that will ensure you're getting more results and a more accurate result page.
- arthurcolle 5y agojust use elasticsearch
- inertiatic 5y agoYou are making a recipe search app without actually paying attention to the information retrieval part of it, which is arguably the most important thing! Using any sort of backend that tokenizes (and why not, lowercases and stems) and does the searching for you is what you want as a first step. ES, or any of the newer fast search engines that aren't that concerned about relevance would be good first steps, then depending on how much you could grow, you're going to have quite tricky but enjoyable journey to optimizing for relevance!