Lekker Labs

2016–present

Curating a searchable, filterable personal recipe collection that evolves as you cook from it.

Side project, in perpetuity

Concepts, UI/UX, branding, data modeling

 

Problem
Recipes come in so many forms, sourced from books, passed down from grandmothers, favorite aunts and at the very bottom of long blog posts. I have searched for years for an app that provides a single point of entry into all the recipes I have access to, which will allow me to search, filter, browse, curate, and annotate.

Role
This is a labor of love – I have designed something like six iterations over the last decade. I’ve iterated on the data model, half-learned and discarded multiple CMSs and Javascript frameworks, chewed through low-code databases and refined my personal “new recipe” form to find a balance between completeness and feasibility.

Outcome
I still haven’t cracked this nut. I don’t know if I’ll ever finish it, but I keep coming back to this problem and continue to be able to find something new in it.

Visual identities and UI concepts

 
 
 
 
 

Current status: reflections from the middle

I’ve learned a lot over the years about this space and this problem and I keep coming back to it because it feels unsolved. I’ve oscillated between trying to make this a Real Thing and keeping it just for myself. I’m still learning how to balance strict adherence to a pure data model that allows for the most robust filtering options with ease-of-use when adding recipes. Some days it feels like I’m designing a data catalog, other days it feels like a food blog. They say to write what you know, I guess.

Below I’ve laid out the latest data model and listed some of the guiding principles for the project. If this problem gets you excited, I’d love to chat.

Findability

Searching all recipes you have access to (book indices, all recipes) and filtering by key criteria (time active, vegetarian-friendly, make-ahead, good for summer). This is both a data and a UI/UX problem.

Maintainability

Easy to add a new curated recipe to the collection (or index a new source when you buy a new cookbook).

Flexibility

Original (canonical) recipes should be easily augmented with personal annotations, variations, and ingredient substitutions.

Usability

Cooking from a recipe should be fun, not stressful. Each step of the journey, the UI should be focused on solving for your current pain points:

  • Finding the right thing
    What can I make with these 3 leftover egg yolks? Which cookbook is that watermelon feta salad I made last week in?

  • Evaluating feasibility
    Do I have the time and ingredients? Would this be a good side for roast chicken? Can I make this a day ahead?

  • Gathering ingredients, mise-en-place
    How many eggs? Can I substitute limes for lemons here?

  • Cooking, serving, and storing
    Which steps should be done simultaneously?

  • Reflecting

    Did this take more or less time than expected? If I deviated from the recipe, how can I remember how it turned out?