Hi Stephen, David, Parker and company! Congratulations on the launch of your new great product BT Server 2.0. And how can we ever thank you enough! Existing developers should be very excited with it. But maybe some of your near- and long-term future most loyal clients will come from our ranks, the new aspiring developers with tons of new ideas but with bare knowledge of programming yet. Just wishing that although its obvious that getting the Server 2.0 to some level of maturity - and reaching a critical mass of plug-ins - you will be so kind as to pause for a while, sometime, to gift us with the essential screens in BT Android 1.5 like display of PDF & word files. Don't want to disrupt your momentum in completing the Server 2.0, though. Thank you.

There's been a few posts about this and certainly some confusion. Without getting to long winded, in essense v1.5 screens are the same thing as Plugins. The difference is only in the way they are packaged up. There are some subtle differences but the Objective C and the .java are the same. In essense a Plugin-package is this code + some other supporting files to work in the control panel. So, with that being said, our development efforts on plugins are the same as our development efforts for v1.5 - it's the same stuff. This means we aren't wasting time. However, it does mean that we did spend nearly 2 months totally re-engineering this idea. The fact is, we had too! It was getting to the point where we had so much unfinished code out, so many confusing, non-documented, very hard to understand 'ideas' that it was ending up costing us literally hundreds of hours of support time and forum posting explaining, etc.. Our inefficient forum doesn't help either! The bottom line is that we struggle bigtime with the fact that everytime we thought 'few more days' a server died, the traffic doulbe, iOS 5 came out, etc, etc. There simply wasn't a way to keep up recently. This new approach, given time, should really help. It should help us and the audience. We are trying to separate the buzztouch 'core' app from all the screens so we can easier explain and teach how each part works. And, like you know, we can easier develop new 'parts' without having to constantly re-engineer v1.5, v1.6, v1.7, etc. And, most importantly, we can FINISH the darned screens we've already started. So...you'll begin to see some changes in your control panel once we get all these plugins / screens done. The changes will HELP you, not hurt you. Dont' get hung up on the difference between the new way and the old way, it's the same thing with a different set of terminology so we can all understand what the heck's going on! Funny. Lastly...we totally agree, 100%, that the existing core user-base is extraordinarily important and we care very much about your experience and level of success. Aspiring devs, with hardly any understanding of all this and even less experience are the driving force behind this and we think literally everyday about how to continue to help that audience without burying ourselves in phone, email, forum stuff. The fact is, the enthusiasm brought to the group by the aspiring devs, vs. the seasoned devs is refreshing. Back to plugins...(oops, v1.5 screens), they've been waiting far too long......night.

Thanks David!!

Enlightened! Many many thanks David. It makes perfect sense indeed. Sorry that it wasn't apparent to my little brain. You probably do mind-numbing coding almost all the time...yet able to do strategic-level instantaneous re-calibrations mid-way. I declare my loyalty. To the Buzztouch community: Why don't we say Buzztouch App or BT App all the time when referring to the apps created with BT? I don't know but, David, you probably reached some near tipping point with the release of the BT Server 2.0. On my end, meanwhile, i'll try to catch up with others and complete my first batch of Buzztouch Apps. I'm sure most of us new and aspiring developers will settle with the self-hosted BT Server and stay hungry for more and more plug-ins. But really hoping that the new plug-ins will be carefully thought of to best serve the varied needs of say, individual developers with bare needs (to start with) to those that can afford the most sophisticated of plug-ins.

I am happy that aspiring developers can bring such a refreshing motivation to the team at buzz touch , as always you guy's rock and it's great to know that a aspiring developer as myself means this much regarding the development here on buzz touch Thanks!!