Would anyone be interested in trading Recipes and Ingredients files from their Android version of eLiquid Recipe Manager Pro? I am sure this is also possible with the iOS version but I don't currently have it installed on my iPhone for testing.
It takes a small amount of computer knowledge but I am sure most anyone here can figure it out. On Android you simply go to the internal SD card. Goto the folder "Composed Chaos", inside that folder you go into the folder "eLiquid Recipe Manager" and then finally the folder "backup".
You then copy over "ermIngredient.db.backup" and "ermRecipe.db.backup" to your desktop or Google Drive, DropBox, etc.
You then download a SQLite Database editor or Browser and open "ermIngredient.db.backup".
Open table "Ingredient" and it will give you a listing of every ingredient name that you have saved.
I currently use this to add ingredients so that I can Copy and Paste the ingredient name and full description from the Web site I am buying them from.
This can easily be expanded by trading the backup files between all the users that would like. The result would be a complete and accurate listing of every manufacturer's products and prices.
Doing the same thing to the file "ermRecipe.db.backup" and we would have a portable cookbook with thousands of recipes.
This would allow a simple port of it to the website. Also while the file is passed around people can add notes or a rating system in the description.
I'm the author of eLiquid Recipe Manager Pro for Android. First, there is no iOS version. Yet. Developing for that platform is expensive, and I'm not quite there yet. I only make a small pittance each month on sales of Pro and ad revenue in Lite. But I have been actively learning the platform recently and hope to have the necessary equipment soon to port eRM to the iOS platform.
Second, the next version of Pro (in public beta right now) will include the ability to directly backup and restore to Dropbox, thus allowing you to also sync data changes between devices sharing access to the same Dropbox account. Once this release goes live, the next feature set I will be working on for the Android app will be a way to share recipes to a central website. It's going to be a huge endeavor, but one I think will be beneficial for the entire DIY community.
And as always, I am always looking for feedback or suggestions on the app, and constructive criticism is always welcome.
Matt Williams Composed Chaos
First of all I must say I LOVE YOUR APP. I have tried them all and I always go back to yours. I had originally looked into the db file to add all the ingredients that I had just purchased. There is so much potential if everyone shared the same db file.
Every ingredient could be in there so after someone orders some new flavors they would be able to add it to their personal db. They would just select the manufacturer and then pick the flavor or item #. This way everything is standardized. I hate finding a recipe and the flavors are not very clear. With about 10 different orange flavors and none of them exactly match the one in the recipe. With the item number option you could even assure you have the same version of the flavor. Often times when they make a new version the flavor is weaker or stronger. You could also change how much of a ingredient you have left in the bottle and on things like dairy flavors it could warn you when the taste is about to turn. It could also include any warnings or notes like "This flavor is known to crack plastic tanks."
When creating and sharing a recipe it would know, use db field instead of the full name. It could give different levels for drippers and tanks. It could also include recommend steeping time, best ohm and best voltage.
When you go to load a recipe you select dripping or tank. You could then select which recipes you would like to make and the volume you would like to make. If you are using a tank it would warn you to change to the metal tank. It would add up how all much of each flavor you would need and compare it to what you have in stock. This would give it the ability to make out a shopping list. It could even calculate how much of each item you have since it knows what you made and how much of each flavor it used.
You could even do something like 3 recipe downloads a day limit. This will help control bandwidth. A small in-app purchase could increase that number, like $0.99 for 50 downloads. You could also have a point system. For every rating you make you get points toward downloads. If you make a comment you can get more points. That comment could then be upvoted or downvoted and once you get a certain number of upvotes you get more points. Once again since the system would know what recipes you have made those would be the only ones you could rate, comment or vote on.
These points could be used for several things, like buying downloads, unlocking features like "What can I make with what I have" or even a request area. If there was a recipe I wanted like Dr Pepper I could offer 50 - 200 points. If the flavor is ok you would give them 50 points, if it was spot on they would get 200 points.
This would also open up things like contests. People would vote on what clone they would like and the winning clone would become a contest. People would submit their recipe for it, everyone would get a free download of that recipe and then vote on it. The one with the highest score gets 1000 free points.
So many things could be done with that level of standard information, those are just a few off the top of my head.