Sorry buddy but I just discovered this. http://www.epicurious.com/services/mobile/ipad
I am building a website to showcase some of my recipes of things that I have been making every weekend using products from an urban farm in South Florida. I installed the Recipe.module which doesn't work as well as I would like. It has great functionality and the community is hugely passionate about its development but it makes it difficult to input and theme the ingredient lists. So now I'm a little bummed that I have to rebuild the recipes with CCK, taxonomy, and Views. Ahh, Drupal development.
Well, looking for inspiration I thought about seeing how other recipe databases handle their information. They, at epicurious.com, must have a few interns who spend their days adding the ingredients to all the user submitted recipes because I submitted one and it didn't give the grocery list option. I was imagining that through some Regex magic it could figure it out. Nope, not that cool. Who understands regex anyway?
Well, I'm just going to make a field for description, ingredients, preparation, yield, servings, and notes. With a tagging vocabulary to include all major ingredients such as leeks, apples, pears, butternut squash ect.. I have to admit you were correct.
However, I did have a look at the pictures of the iPad, iPhone apps on epicurious.com. I'm not sure how you have moved above that. How about a branding approach? Find somebody with a collection of recipes who wants to brand them, for example, publix. Sometimes Publix gives out mini cookbooks ect, or some other person who needs to market a cookbook, perhaps for a special diet like Jenny Craig. Create a recipe database on a drupal site and drive the content through an iPhone and iPad app. Keep it simple as a marketing tool for companies. Just an idea.
My other idea is to create a Git hub, CVS functional website for recipes. From my experience most recipes suck. It would be cool to have good recipes with "version control". Using revioning.module, comments and five star rating system people can submit forks to a recipe that will be placed under development. People are really passionate about food and a website where people can fight about the best recipe could really be very active.
I wonder how that would work. A recipe is submitted with a maintainer and there is an issue cue and people can fight about it. Then the dev version can be updated based on reviews and ratings. Who knows? The approach hasn't been done before and like I said most recipes out there actually suck.