I wanted to note the status of the various versions of BT for my own records. However I see others going down the same path I have with eg android functions that don't work, so I thought it may be a useful record, particularly for others just starting out with BT. My Background: Now, I'm not a programmer, nor do I aspire to be, but very much attracted to the BT concept of rapid development without the need for code. It's been a steep learning curve, so it hasnt exactly been rapid development (think SDK's, xcode, eclipse, different BT versions, etc), but its been a good foundation building experience.... I hope. I developed an app in VT1.4. Easy and simple to use, but to get some more functionality to appease Apple I moved to BT1.5, BT 2.0 plus also installed BT Server. After installing the latter and starting an app with BT2.0, I found some of the essential functions I wanted were not yet available, so I moved back to BT1.5 So here's my summary: >BT1.4 - easy & simple for Android as no approval issues like Apple. >BT1.5 - offers more native functionality to help with Apple approval. Includes the commonly discussed functions of offering a Quiz (also in BT1.4), but also a photo gallery and photo uploader. Creates impressive apps for Apple, but disappointingly little functionality appears to work for Android yet (a common reference to an external site suggests solutions, but never seems an easy exercise to pin point the solution). >BT2.0 - seemed to have less "off the shelf" native functionality (plugins) currently available (eg quiz, RSS, image uploader/ feeder) than BT1.5. Maybe a programmer with some coding sees this differently?? Seems to work ok with android though never extensively tested as had to give up due to lack of required functions. >BT Server - as per BT 2.0 So that left me to focus on BT1.5 which I have summarised below: BT1.5 Function/ IOS/ Android Menu - List/ OK/ ~ (1) Custom URL - Webpage/ OK/ ? (8) Custom HTML - Text/ OK/ OK Multiple Choice Quiz/ OK/ X (7) Share via Facebook/ ? (2)/ ? (2) RSS Reader (news)/ OK/ X (3) Image Gallery (flickr api)/ OK/ X (6) Image Emailer/ OK/ X (9) Image Uploader/ ? (4)/ ? Splash Screen/ OK/ ? (5) Email Us/ OK/ OK (sorry about the lack of a table) NOTES 1. Android format/ colours no style like IOS 2. Unable to test as couldnt get api for business facebook page ??? 3. Error: "Look at the BT_screen_rssReader.java file" 4. Seemed to lock on camera image after photo taken (need to test more as used alternative) 5. Image only part fills screen 6. Error: "...process.com.[app] stopped- Force Close.." 7. Error: "Look at the BT_screen_quiz.java file" 8. Loads some url ok but then app locked up 9. Error: "Look at the BT_screen_Email.java file" COMPARISON OF AVAILABLE FUNCTIONS/ PLUGINS BTv1.4 Sub-Menu (holds more screens) Call Us Email Us Custom Text Custom HTML Custom URL / Webpage Streaming Video YouTube Video Streaming Audio RSS Reader Fun Quiz Single Image Single Location Map Multiple Location Map MS Excel Doc PDF Doc MS Word Doc Share via Email Share via Facebook Share via Twitter BT V1.5 --- Menu Screens Menu (List) Menu (Buttons) Menu Search --- Content Screens Multiple Choice Quiz ** Custom URL. Webpage Custom HTML. Text YouTube Video HTML Document PDF Document Word Document Excel Document PowerPoint Document Location Map RSS Feed ** Image Gallery Image Uploader ** Image Emailer ** Streaming Audio Streaming Video Load Custom Plug-in ---Settings Screens Show Device Info Allow/ Prevent GPS Login Screen --- Splash Screens Image Splash Screen --- Other Actions Launch a Native App Share via Facebook Share via Twitter Share via Email Share via Text/ SMS Email Us Call Us Text Us (SMS) ** above functions currently not avaliable BT2.0/ Server BT2.0/ BTServer 2.0 ---Menu screens Menu Buttons Menu Simple ---Content Screens Image Gallery Excel Doc Custom URL HTML Doc Location Map Blank Screen Word Doc PDF Doc Custom HTML / Text PowerPoint Doc --Splash Screens Splash Screen ---Settings Screens Allow GPS Login Screen Device Info ---Other Actions Send Email Call Us Share via SMS (Text Message) Launch Native App Share via Email Send SMS (Text Message) Suggestions: - Ideally it would be great to maintain a status summary of known issues on each function as it would save a huge amount of time wading through the forum looking for solutions to errors and issues. - perhaps the forum could also be organised around functions/ plugins. Summary: The concept of the BT Server is excellent and my understanding of the concept to add plugins in the future would be a great asset. As to the need to have good programming/ development skills, it seems to be an advantage at this stage. However I take my hat off to David and his team for what they have provided and also their responsiveness. That also extends to the forums great support by many people who genuinely want to help and provide specific direction and links to address issues. Thank you very much David and members for all your help. However to make it comparative to other app builders it would be great to see plugins like GPS coupons, GPS location notification, Push notifications, QR code reader, QR code loyalty coupons, loyalty coupons, mcommerce, wysiwig screen simulators, etc. Is there away the development community can contribute to get these built? I'm also still left with the question as to how much native functionality can be built within the BT platform. This extended a little more than just a status summary, but I hope this helps. E&OE PS I don't profess to claim my understanding of BT is anywhere as comprehensive as many of the more respected veterans in the forum so if anyone has any clarification, please feel free to note.

Excellent post, informative and useful, thanks. It might be worth putting this post in the wiki too (not sure how much it's used at the moment) so, as features become available the post can be edited. I bet you'll find that there are plenty of people trying to get their heads around plugins, which eventually will end up as part of the development in some form. And pretty much any native functionality can be built in to the BT platform. I find it much tricker than writing code into native apps (sample code), but it is possible.

MCappy exactly my comments the other night, what works and what does not....... this is very welcomed in my book. Thank you for your efforts

Excellent summary. A comment I made in another post today is that one of the features brought by BTv2.0 is that you'll no longer have to recreate your BTv1.4 apps into BTv1.5 then into BTv1.6 into BTv1.7 and so forth. That's why BTv2.0 was created. As David@buzztouch commented in a post "the v1.4 to v1.5 to v1.6 insanity had to stop." (paraphrased). As the maintainer of the 'external site' MySkylla's Guide to Buzztouch, I try to first inform as to the functionality of the working screens in Buzztouch (especially BTv1.5 Android, which has the most problems.) and what's available. I give credit to anyone posting a Solution or link to their post when I post a Solution. I started in Oct '11 and feel that my true understanding of Buzztouch has evolved considerably beginning in Dec. Just figuring out what is what is difficult enough besides trying to document everything. I have found a few solutions, but mostly I document solutions and possible solutions and help some find the start to solutions that other have started. I also provide a 'quick start' to understanding how to create your apps. I'm android and your iOS so you may not have benefited as much since my understanding of Android is much greater than iOS. Searching the Forum is difficult and if you don't know what the magic word you're looking for it's almost impossible. I hope to make it easier for you to find whaat you're looking for. My contribution to your notes: NOTES 2. Face book share for BTv1.5 Android doesn't work 3. RSS Android BTv1.5 doesn't work use RSSinclude works very well. 4. Image Loader Android BTv1.5 doesn't work. 5. Splash Screen Android BTv1.5 has a bug, don't use it. 6. Image Gallery Android BTv1.5 doesn't work use flickr 7. Quiz Android BTv1.5 doesn't work use HTML quiz search google for your choice of quiz. 8. URL BTv1.5 & BTv2.0 Wheel of Death & solution will fix url problem (problem also found in BTv2.0 very easy fix.) 9. Image emailer Android dosen't work (be creative store image else where and send link to image.) www.myskylla.wordpress.com To anyone starting to use Buzztouch I understand the desire to use BTv1.5 iOS. (Android users have almost no reason to use BTv1.5.) But consider the long term in making your choice. BTv2.0 will have excellent support, and in a future not to distant, will have much more than will ever be possible in BTv1.5 iOS OR Android. You ask is there a way, well there is: Plugins Fred

Awesome post. @Bigfishtools shared many of the same thoughts a day or so ago (as he mentioned). For sure there's lots going on in our quest to help folks. Many of the things we do are helpful to very few, many of the things are helpful to a bunch. The ultimate goal is to marry the simplicity of v1.4 with the flexibility of v2.0 - not an easy feat. But, we are 100% convinced that most of the items listed in this very impressive post we'll be addressed, improved upon, and extended even further as time goes on. Plugins are the answer to these ideas. It's very difficult for folks that don't understand how iOS and Android "work" to imagine being able to create their own plugins. We dont' expect very many folks to do this. Probably a very low percentage of the overall audience. However, the gap between the 20 or so screen types available now in v2.0 and the 35 or so available in v1.5 is not too wide. Achieving, the "simplicity" of v1.4 in the new setup is a matter of walking folks through the process step-by-step in the beginning so they can see some rapid results. We have a few ideas up our sleeves to accomplish exactly this. Many folks that visit the site do have expectation of us being "like other app builders" and offering similar screen types and features. This is normal. However, because most app builder services are exactly that, services, there is a big difference in our approaches. We are evolving a software package that helps app owners take total control of their app making futures. We are not focussed on providing compiling, submission, design, and other such services. This requires that our end users have a Mac and Xcode (thanks Apple), struggle through difficult Android / Eclipse issues (thanks Google) and understand that some under-the-hood work will be necessary if you want to create a compelling app that you control 100%. Trade offs everywhere. Our road map is VERY long: The first four items are most important: 1) New Site: The line is almost drawn through this item. The transition is getting easier by the day. 2) Optional paid upgrades: Moving from 100% free (and unsustainable) to some paid options is very important. Not because we're strapped for cash but because allowing folks to "do anything" without any commitment causes a very large amount of confusion and support requirements. Limiting new users to some basic volume cuts down on the support and "issues" in huge ways. We need to have a clear message of what the system allows and does not allow "for free" so everyone is on the same page. These details are already much clearer today than they were a week ago so we are almost through this item. 3) / 4) Debatable which is more important. Rolling out buzztouch U learning modules and additional plugins is very very important. And, for most existing users, these are more important than #1 or #2. Of course it is, they already understand what we do, are used to getting anything and everything without any commitment or cost and simply want bigger, better, faster. Makes perfect sense. However, from day one, new users to our site have never been given a fair shake at good learning modules, documentation, and loads of plugins that "just work." Instead, it's been a sort of free for all with some folks getting it and some folks giving up. buzztouch U and a steady stream of additional plugins should help with this. All we really want to do is make new plugins. Really, thats what we are best at and enjoy most. However, because the scale of this thing got so big, so fast, it became painfully obvious that we can't just code screen after screen after screen without a solid infrastructure in place. Consider this: For every new screen we introduce, regardless of how simple, we are flooded with emails about extending it, changing it, customizing it, making it work on Windows (funny), and on an on. Almost funny to think how naive we can be sometimes. A solid infrastructure should help curb this. Roll out a new screen, teach folks how how it works, give them a way to use it without a weekend long commitment and move on to the next one. Yes! As usual, you're genuine and constructive criticism is a blessing and we do not underestimate the value of each and every one of your contributions - they are tremendously helpful. Given time we'll all look back at this amazing project and give a tiny smile because we were part of it back in 2012. Headed to LA for the weekend. Laptop connected to backend, coding away and moving forward... d.

Wow This was the best post so far I have read. This has given me the proper perspective what is and what is not. Thanks David and MCAPPY and all the others. My confidence just got boosted to know that you guys are on it and that we will see more in the near future. Excellent, excellent excellent.