[jka]

As a fairly intentional design decision, you need to provide context from your kitchen - a search engine query, essentially - before you see results.

The concept is that RecipeRadar will ultimately help you track your kitchen inventory (all on your own device; there are no user accounts), and then the search step will disappear into the background - you'll be straight into browsing recipes that match your context.

It's not there yet and I'd appreciate hearing about how you like to browse recipes in case that's something else that can be supported.

[nickff]

You may want to provide 'suggested cupboards', with a limited selection of multi-use ingredients, to show how the app can help make the most of ingredients.

[jka]

That's a great idea - "kitchen staples", perhaps? Thanks!

[nickff]

No problemo!

Sure, you may want to come up with a few different sets, perhaps Italian stuff, Asian-focused, vegetarian, etc.

[jka]

I've translated this into a rough use case / spec at https://github.com/openculinary/frontend/issues/172 in case you'd like to follow along.

[nickff]

I definitely will! Thanks for the heads-up!