But, I'm not sure how useful it is in this packaging.
The service that makes a shopping list for me for a given dish seems valuable. But the service that tries to lay out quantities seems sketchy. All you're providing is an ingredient list, not the technique; to get technique, you have to click through to one of a zillion recipes, and none of the ingredient lists in those recipes corresponds exactly to the ingredient list in your app.
Also, you need to do a better job with proteins. You can't make duck confit with "N pounds of duck"; you need duck legs (also fat, which didn't come up in the list at all). Similarly, chicken paprikash is made with thighs, not "N pounds of chicken". The solution to this is probably just to break animals up into retail cuts in your database.
There's a genuinely valuable "recipe lab" product to be built using a database of flavor profiles (like The Flavor Bible), a database of ratios (like from Ratio), and a database of core techniques ("roast", "braise", "fry", "aromatize", etc).
One thing that'd be neat to do would be to scrape flavor pairings from your database of recipes, do build a bottom-up "Flavor Bible" instead of trying to figure out a way to get the rights to the Flavor Bible itself.