Question, I Thanks to buzztouch (and many youtube tutorials) I was able to successfully create an app that has bridged the gap between our school communication and parents, students, and community! It was so successful that the district has taken note and is going to purchase apps for the remainder of the schools. As excited as I am I am getting increasingly concerned about the licensing of the app. I know there is a GPL associated with the app but I am needing some help further understanding what I need to do in order to sell them. I would really appreciate any help. I am a teacher and want to make sure this is done correctly. All I was looking for was to solve a problem I have with my students and yeahhhh buzztouch helped with so much more.

Hi in McAllen: This is a common problem. There are lots of buzztouch users that solve specific problems for specific verticals like schools, a business category, etc. Considering the license requirement is the responsible thing to do. You have a few choices and a few ways to do this. When you download the source-code for an app from the control panel, it comes with a license. This license grants you the 'right' to do whatever you want with the app. It's yours. Selling your applications source-code is not a problem. Where most people get stuck is what to do after that. Who 'owns' the app, who takes care of it, who is responsible for it in the App Store, etc. These are diffcult questions and each organization has a different requirment so there are not canned answers. What most folks in your position are doing is creating the applications and maintaining control of the apps in the App Store. This approach allows them to charge an ongoing service or maitenance fee to their customer (the school district). Simply put, create it, demo it, make an agreement, then maintain it to your customers expectation. Another approach is a one-time fee. You can easily create an applicaiton that does not depend on the buzztouch control panel. This type of app may or may not pull content from the web. In many cases, the web-content in these types of apps comes from the schools website. This means you'll end up workign with the schools webmaster to design the content to be included in the app. This idea allows to you sell your services (app creation) for a one time fee then require your end user to maitain it. In this case, many of the entries in the BT_config.txt file (inside Xcode) will show URL's pointing to the schools webserver. Hope this makes sense.

You're told this all the time but you are awesome and I appreciate the part that buzztouch has played in public education in Texas. So, my next question is, where should I put the license and where the heck do I get it from. This is all tough stuff. Much appreciated.

Giggles... 'where do I put the license' If you don't need anything special for the School District, simply leave the license in the project when you compile it. Nothing more is needed. iTunes may ask you if you have a special agreement or terms and conditions your users need to agree to before using your app. In iTunes, ignore this, you're needs are not that complex. If the school district needs a copy of the license agreement, I would simply copy the one in the Xcode download, save it as yourName.txt or something else and give it to them. They may be looking for assurance that you have the right to sell what you made. Finally, the source-code you download it YOURS. You made it. Your app is different than any others (it's close to others because it's based on buzztouch but it is unique in many ways) and the license that comes with it grants you the right to sell or redistribute it as long as the terms listed in the simple license are followed. Basically, it just says don't remove the existing text. You can always append more text to the end. Don't get hung up on the license, you're providing a valuable service and have every right to call your project 'your work.' It doesn't matter that you found a cool tool to make your software, you made it, just like if you wrote it from scratch. Thanks tons for the kind words ;-)