where ya at @Haze Vaporizers
Not keeping in contact with It's original followers and helping hands. It's not the same Haze Technologies I grew up with.where ya at @Haze Vaporizers
Is that just to start pre-orders or actual shipping to customers? For the guesstimated late November early December.Hi Guys
Our test results have been great with the changes we have made. We are picking up a unit from our engineers by Thursday and will shoot the video. We believe that we have a winner now. We still have to go through few more test rounds but mainly mechanical. If all good, we are looking at late November, early December launch.
That is shipping to customers. We are planning to start preorders in the next couple of weeks.Is that just to start pre-orders or actual shipping to customers? For the guesstimated late November early December.
Should be posted by the end of this weekend.
Bruh, relax.I'm sorry but I feel like you're losing some trust here. You've now said this many, many times, and never really even acknowledge the delays.
Bruh, relax.
I don't need to relax, as I'm not getting mad here. I'm just saying that they've now had a mix of guaranteed updates and silence for the past many months - I doubt I'm the only one who feels this way.
Dude they find unexpected issues, they need proper testing. I can't wait to know more about this unit, but I'm not in a hurry and will rather have a well finished unit working amazing by next year than having a shitty unit full of issues tomorrow
There are at least 20 people from 6 organizations involved in developing this product at the moment. Not counting the beta testers who provided valuable feedback. We love the community and want to stay in touch with you all. When we are asked about an update which is pretty frequently (that we deeply appreciate by the way) , we had three options:Look I never blamed them for the delays and agree it's totally understandable.
What I said is that they now every week say the big video will be end of that week, and then the video isn't released and the same thing happens a few days later.
I'm happy to wait and am not being impatient at all, I'm just a bit annoyed that @Haze Vaporizers keeps setting deadlines that they don't keep, instead of just saying it'll come soon. I also appreciate the updates - again the plethora of unkept deadlines is just somewhat annoying.
I didn't mean to offend anyone or come off as impatient.
Personally, I'm happy to follow the thread and not give you extra workThere are at least 20 people from 6 organizations involved in developing this product at the moment. Not counting the beta testers who provided valuable feedback. We love the community and want to stay in touch with you all. When we are asked about an update which is pretty frequently (that we deeply appreciate by the way) , we had three options:
Option 1: Copy/paste this everytime a member asks an update: We are given some updates but sorry we cannot share or tell you until we are certain in order not to disappoint you.
Option 2: We don’t even respond and be MIA until we have something certain to share so we do not disappoint or annoy anyone.
Option 3: We stay connected, be transparent. Share as much information as we can that come from engineering, production, design teams in terms of progress, expected shipment and delivery dates etc. by judging a level of certainty but still assuming the risk of certain disappointment if some dates cannot be met due to the nature of a product development life cycle.
So we chose option 3.
I understand that we annoy you with this and i do apologize. I can make a note of your username and send you PM once we have more solid posts. For example, as soon as the video is posted, i can send you a PM to check it out. That way, you do not have to follow this thread and read all other posts which the dates may be missed. Please let me know. Matter fact, i can start a conversation list with all other members in the same expectation level as yours. So that list can get information after a solid milestone is posted. I assume that the greater majority want to hear about the updates as they happen without being annoyed or disappointed at the exact dates since we are clearly close to the finish line on this. So we will keep posting on the thread and keep answering questions here.
There are at least 20 people from 6 organizations involved in developing this product at the moment. Not counting the beta testers who provided valuable feedback. We love the community and want to stay in touch with you all. When we are asked about an update which is pretty frequently (that we deeply appreciate by the way) , we had three options:
Option 1: Copy/paste this everytime a member asks an update: We are given some updates but sorry we cannot share or tell you until we are certain in order not to disappoint you.
Option 2: We don’t even respond and be MIA until we have something certain to share so we do not disappoint or annoy anyone.
Option 3: We stay connected, be transparent. Share as much information as we can that come from engineering, production, design teams in terms of progress, expected shipment and delivery dates etc. by judging a level of certainty but still assuming the risk of certain disappointment if some dates cannot be met due to the nature of a product development life cycle.
So we chose option 3.
I understand that we annoy you with this and i do apologize. I can make a note of your username and send you PM once we have more solid posts. For example, as soon as the video is posted, i can send you a PM to check it out. That way, you do not have to follow this thread and read all other posts which the dates may be missed. Please let me know. Matter fact, i can start a conversation list with all other members in the same expectation level as yours. So that list can get information after a solid milestone is posted. I assume that the greater majority want to hear about the updates as they happen without being annoyed or disappointed at the exact dates since we are clearly close to the finish line on this. So we will keep posting on the thread and keep answering questions here.