So, on paper buzz touch looks amazingly perfect for what I'm needing. My experience in the last 48 hours has been off to a rough start. 1. Yesterday when signing up, I would get a log in confirmation, only to be re-directed to... the log in screen. This AM if finally logged in. HOWEVER, 2. My email confirmation will not send to me... So I am still in the abyss of just trying to check out the product. I've resent the email 3 times... nothing. Experienced users, IS THIS WHAT I CAN EXPECT? .. Should I just turn the other cheek now, while I can? Thanks much - Richy Clark

Generally, no problems. Once before their server had problems, I believe it was due to a app in Austria that was a big hit. Yesterday was a new problem, no one has said why. I believe you'll find it's reliable, then again, if you're the one hit by lighting, doesn't matter if it's one in a million.

Hi Richy,I had similar login situation yesterday, so once you are logged in you can go ahead and resend an email confirmation. You should be good to go. I am new at this as well.

One additional observation, most of the bugs most people find are features that the user didn't understand how to use. The few bugs reported & unreported seem to be fixed quickly. Then one must understand btv1.5 & btv2.0 are beta, so a few problems are expected. Though my observation is that mostly the problems occur because of user errors. Fred

Hi @RichyClark , Please don't give up! Buzztouch is very likely the software of your dreams, but they have had a few technical issues the last few days (and what growing website hasn't!), but David and the crew are generally pretty fast at getting things fixed. Hang in there, and I assure you, you'll be glad you did. In the meantime, check out these doc, and get your environments prepared for when you finally download that code: http://www.buzztouch.com/resources/Things_You_Need_Before_You_Start_Developing_Apps_v1.0.pdf http://www.buzztouch.com/resources/Setting_Up_Your_Android_Development_Environment_v1.2.pdf http://www.buzztouch.com/resources/ If you have any questions, let us know. This forum is pretty responsive! Thanks, Mark

Perhaps a browse of the forum would have clarified the issue? http://www.buzztouch.com/forum/thread.php?tid=CECB6C8CFAFA90C44894201&status=&searchInput=search...&sortColumn=FT.dateStampUTC&sortUpDown=DESC¤tPage=1&doViews=1 Mark, why don't give up? The less people that know how brilliant BT is, the better it is for us!

Thanks guys. That's encouraging. I will wait it out. The fact the the forum is ALIVE is a great plus as well. Will try to re-send that email again.. :)

Hi Richy, I think these are due to growing pains ...remember them ? It's happened before and will most probably happen again. The Buzztouch team does a kickass job to get things back to normal when there is peak activity. They normally sort things out in a few hours. I'd say its more a proof of good heatlh if the servers get overloaded. Means some apps are doing very well. Buzztouch is in infancy, the team is A++, the community is A++ and I guess we are all learning at the same time. Hang around, it's going to be worth it!

This is the platform you want to use for building apps...also, get using V1.5 buzztouch apps...you'll be very happy and can tweak code all you want!! :)

@raveyd...good point about keeping it secret! Forget everything I said earlier in this post! ;-)

Yeah, but you forget that once he gets up to speed he'll teach us a few tricks.

Ah, dang @Fred...another voice of reason! ;-) The more, the merrier I say...I learn a ton myself just by helping people get going! Mark

lol! just a reverse psychology ploy of mine guys. BT deserves to be known by everyone!

Good stuff here. I'm thinking we program in a planned backend failure every x number of days, random of course to keep everyone on their toes. Hmm, Twitter seemed to get somewhere (they seem to be doing OK now) with constant failures for a few years. Facebook died four times during year one and seemed to have finally gotten it together. I think they have a little money and manpower now but I'm not sure? If we planned in a random failure we could surely reach the same level of 'fail' as the big guys right? If we failed on our own, without anyones help, and the backend crapped just enough, we could bypass the automagical overload trigger and continue as usual. But, if we didn't fail enough we could rely on the cool custom buzztouch virus plugin to take everything down for awhile, just enough time to get some press of course and to make us look good because we 'jumped into action to fix it at 3:00 AM again. We've died 3 times (totally down) in the last few years so we'll need to ramp up the cardiac days to get caught up the big guys. Shouldn't be too tough with some good code? Besides, figuring out how to create an attack worm is something I've been wanting to learn. Deploying it on our own backend makes perfect sense. So laughing (and kidding of course). @RichyClark: Thanks tons for finding us and welcome to the gang. For sure we don't have the resources like a Twitter or Facebook but I think you'll be impressed with just how much this thing DOES work, as compared to doesn't. When we grow up we envision a giant data center with a few armed guards like the fancy pictures show on your favorite hosts home-page (not sure they have what they portray?) but until then we'll have to settle for a few dozen boxes full of mice and treadmills, just enough to keep us in app-happy ;-)