|
|
|
|
|
|
by kjellsbells
631 days ago
|
|
|
I'm a long time veteran cook. This may sound a little rough, but the most important feature, bar none, for me, is not getting the recipe in to a recipe app/site, but getting the recipes out. All recipe apps have a finite lifetime far lower than the useful lifespan of the recipe collection. So, imagine a chef puts in the effort, over a few years, and builds up a corpus of a few hundred or thousand recipes. They expect to be able to take those recipes with them when they inevitably migrate to the next system. Example: I got lucky with Pepperplate, in that they used sqlite under the hood, and there was a repo on github that could extract the recipes. By contrast, Cozi is a black hole, and I'm going to have to do brain surgery on my phone to figure out how it works. Never again. I'm seriously thinking of building my own infrastructure in YAML/XML (recipe markup language?) to store the recipes in a standard schema, a LaTeX layer to optionally print the recipes on index cards to give to family members, and some sort of plugin-based extraction method for various websites. Its quite a grind. |
|
|