I would think that it would be an excellent idea to continue on focusing on exactly that instead of adding shiny features. Recipe apps have to fight proven and battle tested procedures already in place in any kitchen worth its name for collecting and organizing recipes. (I know: 1. Print it out. 2. Put it in transparencies. 3. Put them into a folder. Easy and robust.)
I can think of several things that could help you streamline that process and fight the good fight against paper. Apps have benefits but they are slight so it’s not easy.
You could try to further automate the recognition of recipes on sites you don’t yet know. Try to prefill if you can, the standard selection process of the iPad is not all that much fun to use. If everything else fails don’t force your users to go through that tedious selection process, allow them to save the webpage wholesale. Lower, lower, lower the boundaries of saving a recipe. You are already on that path and I encourage you to follow it. Great app!
The goal was to build a tool that suited that workflow the best, while removing the drawbacks of organizing printed stacks of paper: searching through your collection for a specific recipe or a specific category of recipes (e.g. all chocolate desserts).
Thanks for the thoughts, I totally agree on the importance of streamlining recipe saving.
One critical feature I'd like to see is a bulk way to get stuff in and out of the app. If you could sync a directory of text and image files with Dropbox, that would be awesome. I want to be able to load my library into it; I want to get stuff back out easily; and it'd be nice to write my own scripts against the datastore. (e.g. epub/pdf conversion).
Example (hope this comes through ok):
Title: Recipe Title Here
Alternate: Alternate title here
Category: Entree
Flickr: 1234, 3204, 29384
Author: A U Thor
Image: foo.jpg
Some optional headnotes. Usually one paragraph.
Additional paragraphs separated by newline.
* Ingredient Heading
- ingredients start with a dash
- 1 cup milk
- 1/2 small onion, chopped
* Maybe another ingredient heading
- 1 tsp another ingredient
Instructions follow the ingredients, with blank lines separating
the paragraphs.
More instructions.
I'm currently using these text files and a bunch of home-grown software. I started out with YummySoup, exporting to this text format by hitting their CoreData database with a little python app. (You need the .mom file in the app bundle to pull this off.)For my stuff, I got to define the format, so it's pretty simple to deal with. Stuff like mealmaster seems to vary widely in practice and is tricky to parse.
I also allow headings in the instructions, too, so I do have to peek ahead to see if a starred line precedes an ingredient line or not.
My main worry is that people will have recipes saved in all sorts of random formats, and won't understand why the importer doesn't work when they try it on their files, and won't want to reformat them.
Not sure if I can think of a clever workaround for that, though...
* Ability to send page from safari to paprika
* Ability to copy URL from paprika browser (currently the recipe capture comes on when trying to select content of address bar)
* Access to safari bookmarks from paprika
* Online storage and syncing (you can make money on subscriptions)
* Shared recipe book, synced through the cloud, for family sharing (That way my wife & I are able to share one resource)
* Wiki-style recipe editing to make experimenting easier without losing the original recipe.
Hope that helps and keep up the good work.
* By sending from Safari to Paprika - do you mean Mobile Safari, or from a desktop browser? I think a bookmarklet might work well for that....will have to think about it.
* The address bar URL thing is a bug that will be fixed in the next release.
* Good call on the Safari bookmarks, we'll consider that.
* We are definitely planning on doing some sort of cloud based recipe backup/sync/sharing.
I've always been big into cooking and when the iPad came out I figured it would be the perfect replacement for the massive stack of printed recipes I had collected over the years.
But after trying out the iPad recipe apps in the store, I realized that most of them did not allow you to enter your own recipes, and the ones that did were incredibly cumbersome to use. (E.g. having to enter recipes from an external website, or having to fill out 24 fields to get a single recipe entered.)
So the idea for Paprika Recipe Manager was born, and a few months later, it is now available in the App Store.
The basic premise of Paprika is basically an Instapaper for recipes. It comes with a built in web browser that lets you save recipes from the web. (Which is mostly how I discover my new recipes.)
We designed the app to be as simple as possible to create and save recipes. Some of the other apps in the store require you to enter ingredients one at a time, specifying quantity and units separately, and then entering your recipe directions one step at a time. This makes the process for entering a single recipe way too cumbersome and takes up too much time.
We took the opposite approach and basically give you two big text fields for your ingredients and directions. Entry is completely freeform and you can basically put in whatever you want. This also makes it very easy to save recipes from the web (since they can be presented in all sorts of arbitrary formats).
Features include:
Here are a few promo codes to get you guys started: Any and all feedback is greatly appreciated. The response has been fairly positive so far (in terms of ratings and reviews), although there is definitely room for us to improve.I'm especially interested if anyone has thoughts on marketing and promotion. I've done the standard tasks of posting a press release and emailing a bunch of websites/blogs...but don't really know where to go from there. Has anyone had success with a Youtube teaser, or Facebook/Google ads, or buying ad banners on other sites?
Edit - Whoops, managed to post this with a bad url the first time around. Fixed.