Recipes can be protected under copyright law if they are accompanied by “substantial literary expression.” This expression can be an explanation or detailed directions, which is likely why food and recipe bloggers often share stories and personal anecdotes alongside a recipe’s ingredients.
So besides SEO, there's this thing where the recipe itself is basically defenseless against someone stealing it and calling it theirs but the sum of the fluff around it plus the recipe on the other hand can be copyrighted and enjoys all the protections afforded to these kinds of things. So, if say, Jamie Oliver likes your recipe and puts it in a book passing it as his, you can now legally tell him to stop doing that because of said fluff.
I've actually never looked at what the bandwidth and storage costs for my apps could be. But also, they could easily be taken out of the equation by letting me pay for that separately? Inclusion in the mandatory single point of failure that is the app stores _by itself_ should not demand a hefty, ongoing tax
Why is charging a flat fee never an option? Just take $200 and let me do my thing. Taking any % of my income on the regular as a kind of existence tax is detrimental for the ecosystem.
So besides SEO, there's this thing where the recipe itself is basically defenseless against someone stealing it and calling it theirs but the sum of the fluff around it plus the recipe on the other hand can be copyrighted and enjoys all the protections afforded to these kinds of things. So, if say, Jamie Oliver likes your recipe and puts it in a book passing it as his, you can now legally tell him to stop doing that because of said fluff.