> I have a boatload of feature creep ideas for you to reject... Shall I post them here, or DM you?
Ha! Either, or feel free to email me at jeff@umami.recipes.
> Take a pic of a recipe, OCR if can
The app actually has an OCR recipe importer (tap "Add Recipe" > "Scan Recipe"). It uses Apple's native iOS OCR library, which inserts text directly from the camera.
It doesn't support importing from an existing photo yet though -- that's high up on my list to build (after Android).
> else host the pic?
You can upload photos for recipes!
> However, an interesting aspect of the "recipe" app logic is that it can apply to, say, mechanics
That's a really good point. I bet much of the underlying functionality could be re-used in a completely different app focused on something like mechanics. Another example I've thought about is a separate app specific to cocktail recipes, with features tailored around mixology and bar management.
LOVELY.
I have a boatload of feature creep ideas for you to reject... Shall I post them here, or DM you?
-
This is an app logic that works for more than just cooking - but a big thing is OCR a hand written recipe from familial cookbooks...
I still have my mothers, as well as hand written recipes from my grandmother, their friends, etc.
Take a pic of a recipe, OCR if can - else host the pic?
--
However, an interesting aspect of the "recipe" app logic is that it can apply to, say, mechanics
"Here is a recipe for replacing this part/working on this thing"
> I have a boatload of feature creep ideas for you to reject... Shall I post them here, or DM you?
Ha! Either, or feel free to email me at jeff@umami.recipes.
> Take a pic of a recipe, OCR if can
The app actually has an OCR recipe importer (tap "Add Recipe" > "Scan Recipe"). It uses Apple's native iOS OCR library, which inserts text directly from the camera.
It doesn't support importing from an existing photo yet though -- that's high up on my list to build (after Android).
> else host the pic?
You can upload photos for recipes!
> However, an interesting aspect of the "recipe" app logic is that it can apply to, say, mechanics
That's a really good point. I bet much of the underlying functionality could be re-used in a completely different app focused on something like mechanics. Another example I've thought about is a separate app specific to cocktail recipes, with features tailored around mixology and bar management.