I'm practically always cooking with a phone these days. So, I thought I'd make my own app to combat some of the UIUX challenges I think most home cooks still face these days. Despite a plethora of cooking apps.
It's far from perfect, but I think Android users will be delighted with the Web Share workflow. It's the most frictionless way to obtain recipe from the browser(imo).
It's just a recipe scraper now, but I hope to make it more of a tool to help encourage people to steadily level up their cooking game.
I have a general idea where I want to take the UIUX, but this a side quest that I'm avoiding until I include more core utility/functionality.
I gave my self a deadline to post this by March 31st. So here it is in all it's unpolished glory. ----
Note on pricing/cost(since you must bring your own keys):
Each recipe conversion API costs are typically fractions of a cent. You can pretty much enjoy this "pay as you go" model and not go above $1.00 the whole year. Which seems fair(to me) for you to foot that bill. The costs I incur are the monthly server and development costs. I'll have to come up with a way to afford these if it gets MAU, but I think donations would be all I need to keep this going.
I think the primary reason the avg young person doesn't adopt the plethora of cooking apps out there is that: the payment structure is out of balance. I have a lot of speculations why, but i think I'll leave that for another post. ----
PS- Favorite feature:
cooking facts/quotes.
Also, phones and kitchens do not mix well. You are fighting a battle trying to get people to adopt electronic devices in an environment full of water, heat, food, etc.
Personally, I like taking a snapshot(s) of a recipe from cookbooks I own. That way I can bring my phone into the kitchen and leave the recipe book out of the splash zone.
I'm pretty sure people these days frequent their phone to obtain/cook with a recipe they got from the internet. Not everyone does, but I'd wager it's pretty common.
I guess technically you could put a spending limit on it, but from your perspective that's a really long onboarding flow.
See the " ...why install? " link.
The PWA really is only useful when it's installed. It makes it really easy to send a recipe from the browser directly into the pwa. Bypassing having to scroll through any ads.
