I don't intend to keep bringing this up, but some of us are building an Open API flavor database and a new DIY web site for the community. We are a small group of developers from the vaping/DIY community and we want to involve anyone interested in helping.
We are still in the planning stage and now is the time to join if you want to help make architectural decisions. Please comment if you are interested and we'll bring you into the fold.
We have a github repo set up here:
https://github.com/Korlimann/MixnJuice
We are carefully planning, so there is no code committed yet. We have been told by the operator of ATF there is a chance of collaboration, so we are excited about that. We just want to ensure anyone who wants to be involved has an opportunity. Thanks and I promise we'll back off the posts until we actually have something new to share or enquire about.
I'm so excited to hear this and am looking forward to the final product! I can't offer anything to the project except to wish you all good luck! 👍😊
Thanks!
And, you do actually could help us :) While we already have a lot of requested features, you can upvote the features you'd like to see most or even add your own features if you have something you'd really like to see here
​
Any input is highly appreciated and more than welcome!
A few minor suggestions:
- Support multiple bases/PG alternatives (PDO, PEG)
- Sharable flavor stash list that doesn't hide behind a login wall, so people can ask for help here and not require us to have accounts on your site
- tags for flavors (so 'peachlike' could be used for any peach, nectarine, mango, etc)
- exclusionary search (so I could look for recipes containing no strawberry, peachlike, black licorice, and/or vanilla flavors, for example)
- maybe a multi-tier review system, so fake reviews wouldn't be a major problem, but more recipes might get reviewed?
on point 3: at that point would it be better to keep the tags related to the actual component flavours (plus overall profile ones the mixer/reviewers can pick) , and then implement some kind of flavour wheel/matrix?
that way you could have it so that when creating a recipe with peach and mango, it could suggest suitable pairings might be nectarine and apple - kind of like an autocomplete for next flavours?
i suppose you run the risk of a bad system homogenising 'samey' recipes, and stifling the creativity of newbies. i'm not even sure if it's within the scope of your project, but it's an interesting extrapolation of the tag system.
Up-voted due to excellence. Love the idea of an exclusionary search. Maybe it kicks in once you have input at least 3 exclusions - or else you'd be left with a mammoth list? Or is that fine also?
You would be surprised, i think, if you realize just how kany recipes are ruined by the presence of just strawberry or vanilla. But recall the wonder of exclusion searches is that it doesn't limit to just exclusive... I could ask to find grape recipes except for tobacco ones. Or i could search for NeoCitran recipes (lemonade without cooling). Maybe floral recipes I hr han introductory level ones (ie using florals other than CAP Hibiscus or TFA Honeysuckle). Although saving personal preferences for automatic exclusion may be another idea. So someone with a severe pinapple sensitivity could search for 'what recipes do I need one or two morre flavors to make?' and not have auggestions involving pineapple . (luckily not me, but i remember someone mentioning migraines or something when vaping any such.)
Thanks for the suggestions and I think we're on the same page. The current schema for the flavor db takes the base into account and even knows if a flavor is the same as another, with just a different base. I believe all of the others have been on our list, but I'll make sure. I plan to make the review system based on points, depending on different variables, like user weight and such, but we're probably not going to openly discuss exactly how the points work. I dont believe a 5 star system is an accurate enough review system. Thanks again!
Actually, my point 1 was meant for the following: I try to keep actual PG content of my juices below 15%, maybe 20% in extreme cases... but for some recipes, 60% VG is about right, so I'd rather use something like 25% PDO, with the remainder of the recipe being done as Max VG. Now, I can just tweak the ratio after creation, so all I have to do is replace all the extra PG with PDO, and independently work out the weight of that amount of PDO to use, but it would be nicer to have the calculator allow me to specify VG %, PG%, and PG-alternative (type and %)
Here's a clue.
I'm pretty loyal to two true tested suppliers. It'd be the cats pajamas to have my inventory when getting low comprise ( based on my habits of specific use of flavors ) to comprise a list of soon to be need supplies.....and then.....and thennnnn
Do a inventory price check comparison against each other for the best deal........and then.....then......Show me any available coupons or free shipping offers over certain amounts. Like this:
Your total is 44.83 and then a coupon code pops up for 10-15% off over 50.00 and with any 50 spent, you qualify for another 60ml of juice choice.
Yeah, that's fooking epic. It would be a game killer and turn the juice, Coils and accessory market in its head.
Make that happen and take my wallet and the world.
Integrate Vapecrawler into my inventory and give me a clickable link. For juice, pg, VG, Coils, cotton, anything.
Batch inventory management please.
Can you please elaborate? My apologies, just want to ensure I'm not making assumptions.
When adding flavors to your stash the ability to enter volume or weight. Then as you make batches the weight or volume is deducted from your inventory
I support this, hope it works out without dividing various reputable sites and people who are loyal. Best wishes and look forward to giving it a go.