Just going through the excellent Buzztouch lessons but found myself getting completely lost and falling asleep during the very advanced sounding coding stuff in the Eclipse section. I really don't want to be a coder, as such, otherwise I would not need Buzztouch. I thought that the advantage of Buzztouch was that it did all of this coding for you so all I really want to know is how to get my downloaded source code into Eclipse and get it to spit out the app. Anywhere that explains this minus the rocket science?

If you want to be the true owner of your app, including all the source code and intellectual rights, those are the steps to follow. If it sends you to sleep there are other 'easier' builders like http://www.appmakr.com/ - enter some info, spit out a generic app. You won't have control of the design or source code though.

The Buzztouch Process is just such a guide. www.MySkylla.com Fred

I understand exactly what you mean. I too have no coding experience and it all sounds a little complicated when you first start out. The secret is stick with it. Take it one step at a time and use the forums and guides like Freds excellent guides as stated above. Dive in and try stuff out even if you don't go through all the lessons. In a few weeks with the guides and help you will get in this forum you will understand stuff you never thought possible and will gain a lot of self satisfaction in the process. The more you do, the easier it will become.

Hey Barry, Welcome to buzztouch. Like @raveyd suggests, there is almost nothing you cant do with buzztouch ;) Don't spit out a generic application. Make something worth downloading! For guides to get started, check these out: http://buzztouch.com/resources and http://myskylla.com These are great resources to get started with, it will tell you exactly how to get your source code from buzztouch and spit out an application with eclipse. You just gotta check around! Doing the buzztouch University Lessons was a great first step. Cheers, David buzztouchmods.com

Hi Barry, Welcome to buzztouch! Try this super simple, step-by-step, illustrated guide to everything you need to know to get your app up and running on Android: http://www.buzztouch.com/files/howtos/buzztouch_For_Android-A_Users_Guide.pdf If you have any questions, just let us know! Mark

Thanks, Mark. I have been using your guide (found it in another thread). I posted there about the issue I am having. I have followed all of the steps but get the following error: When I try to load the source downloaded from Buzztouch (either using method 1 or 2) I navigate to the root folder it appears in the field (but slightly greyed out) and I get the message " Cannot import com.paleochora.BT_activity_root because the project name is in use". I have not opened it anywhere. It is not open in another application. What is going on? I have deleted all that is in the Workspace folder and tried again. Can anyone advise me please. I am also seeing that I need to go right click on the project and select "Adndoid Tools" but can't find where to navigate to in order to right click on.

Hi Barry, It looks to me like you are trying to import an "Existing Android Project," otherwise it would show up in Package Explorer as "buzzTouch" instead of "com.paleochora.BT_activity_root". So, give this a try: * In the Package Explorer frame, right-click any package and select Delete. This will remove it from Eclipse, but not delete the files. * Do a File...Import...Existing Project, and navigate to the unzipped root folder you downloaded. This should cause the files to get imported into Eclipse, and give a package name of "buzzTouch" * If it throws a Project Properties error, click on "buzzTouch" in Package Explorer to highlight it, right-click, go to Android Tools...Fix Project properties. If you don't have that option available, then you don't have the Android ADT Plugin installed for Eclipse. Let me know how that goes. Mark

This sounds daft, but how the heck do I open the Package Explorer frame? EDIT. Found it! Just doing the fix project properties now...

It should be there by default, but if not, in the menu bar, go to Window...Show View...Package Explorer. If it still doesn't appear, then it's probably there, and minimized somehow. Mark

OK. Here's what is happening now. The import process does not show unzipped files. So I deleted all and then imported the source code again. I fixed the errors by choosing the correct version of Android in file>properties Then I try to run as android application. The emulator works but I get these errors in the console: [2012-07-29 10:49:13 - com.paleochora.BT_activity_root] Installation error: INSTALL_FAILED_MISSING_SHARED_LIBRARY [2012-07-29 10:49:13 - com.paleochora.BT_activity_root] Please check logcat output for more details. [2012-07-29 10:49:13 - com.paleochora.BT_activity_root] Launch canceled! EDIT: Figured it out! The emulator was not running the Google 2.2 8 API. Now my app is running (but not the splash screen for some reason - any ideas about that?)

Are you using BTv1.5 or BTv2.0?

I'd avoid splash screens until you get the rest of your app worked out. They tend to cause more problems than they are worth at this stage. Congrats on getting up and running! Way to hang in there! Mark

Thanks guys. I am using BT 2.0 which is what the videos advised me to do. Don't know why that is not working. Everybody tells me to make the app 'special' and not just basic=boring but, hey. The rest of the app is worked out. Just the SS not happening.

Splash Screen BTv2.0 works, check your theme settings, check splash image name. Also recompile if you haven't already. Fred

It "works," in the sense that the SS option is available, but it's been buggy, in the sense that we've seen lots of app errors when it has been used. One thing to consider is that the user only sees the SS once, when they first fire up the app. Subsequent uses of the app, unless the process has been completely killed, simply brings the app to the foreground, and doesn't initiate the SS again. So, while it's momentarily cook, the real meat of your app is what needs to be unique and special. Nobody is going to buy an app just because it has a cool splash screen! I wouldn't get to hung up on the SS...focus more on the actual content of your app. You'll find plenty of challenges there! Mark

Personally I've noted that some users preffer apps without splash screens, they give a feeling of "slow loading", and this is from user feedback I received. Cheers, David buzztouchmods.com

For iOS apps, I just use the Default*.png files, that are required by Apple, and throw up an image on those. That way I have a nice splash screen that doesn't cause any issues, and I use an image that has to be there anyway! Mark

For BTv2.0 (Android) I use a Splash Screen without problem. Some have noted a problem, but I can't say at this time the plugin is buggy. Perhaps the user is at fault. Certainly for iOS the default .png is an option. Certainly the splash screen can add or detract from the app. Fred

@Mark, that's why I call those "fake splash screens"! I think @David once said not to do that (not sure?), that there's a big difference between the two, but if it's been working out, then great! "'for some reason, they decided to add white text' You must be referring to the text on the launch images. This was added so end-users knew which launch images to change after they downloaded their projects. You may understand this, 99% of our audience does not. It's expected that new launch images will be created and provided by the app owner before submitting to App Store." - David@buzztouch Cheers, David buzztouchmods.com

@Fred missed your post... yep, I think the design of the splash screen most likely has a lot to do with user feedback. I believe some users like to let the splash screen stay up for 5 seconds, while I prefer 2 at most! David buzztouchmods.com

Not quite sure how the user can be at fault, when the app crashes and the stack dump points to the splash screen. The user literally has no interaction with the splash screen. The issues I have seen appear to be related to an app opening, a splash screen being displayed, and then transitions back and forth to other screens. Even from a developer perspective, there is little they can do to influence the process in a negative way. You create the splash screen, give it some properties, and assign it. Not a lot else. Just because it's managed to work for you, isn't a good reason to point towards user error in this case, unless you have dump analysis to support that. Anyway, I still suggest not getting stuck on this small part of the app, and rather focus on the meat of the app. I think we can all agree on that. Mark

Another "Splash Screen" option is use an html doc with a redirect. Works well. Fred

Just because it's managed to work for you, isn't a good reason to point towards user error in this case, unless you have dump analysis to support that. "Some have noted a problem, but I can't say at this time the plugin is buggy. Perhaps the user is at fault." I can't say and perhaps are both qualifiers, I don't have data nor does anyone else to my knowledge. Therefore I can't say. But I do take note of what some users are saying. When I can replicate the problem then I'll say there's a bug. Did so in BTv1.5 (Android). Since it works for me, it may work for others. IMO we need more data before we say it's buggy, but that's my opinion. Fred

I just added my image url and set it in the global. http://thepaleochorasite.com/palappsplash.jpg

Not gonna engage you in an argument on it. Just saying it's a minor part of the app, and there are bigger fish to fry! Mark

Never had a problem with splashscreens either. They just work. Perhaps a setting, or combination of settings, isn't working as it should?

Try updating your Config file. Fred

Thanks, Fred. How would I go about doing that?

Thanks, Fred. How would I go about doing that?

Thanks, Fred. How would I go about doing that?

Copy the Config file from the control panel and paste into the BT_config.txt file in the source code. Fred

Thanks, Fred. I wasn't being impatient, I don't know why that was posted 3 times. I guess it happened if I refreshed the page. Sorry.

Mark, I am a bit lost in getting the API for maps used in my app. You say to generate the MD5 fingerprint for the debug & release certificates we run a command. How and where do I do that? Thanks EDIT. I used Keystore plug in in eclipse to find the data. I have added the Google API to the string. So my next question: Does that mean I have to re-compile my release app or will these changes take effect in the app as it is (I compiled the release version before getting the Google maps stuff as I needed the release certificate details)

So I asked someone to test it on an Android device. Here was the feedback. Hard to make sense of it and can't imagine where to start fixig it...Any advice? Here is the tester feedback: "OK Barry, loaded it up ok then it crashed,loaded it again no welcome screen but loaded, the map loaded but with no detail, all other tabs (custom URL pages) all load no problem, then it crashed I have to force it to close then restart it the welcome screen popped up then it crashed, now all it does is give me the welcome screen then crashes. A few bugs in it. keep at it though its a good little app"

*** Does that mean I have to re-compile my release app Yes, any changes in the source code require a new binary. *** or will these changes take effect in the app as it is Only changes in the control panel well be reflected without a new binary. *** (I compiled the release version before getting the Google maps stuff as I needed the release certificate details) No problem, its what you need to do. Fred

To fix the map issues I suggest you read my Buzztouch & Google Maps article. www.MySkylla.com Fred

Before you compile a new binary update your Config file. Fred

I got the info regarding the maps from your article (well how to use the eclipse plug in to get the key etc) So, I will download the source code again and add it to a new project and re-compile. I just checked the pages with the maps and all looks ok in Buzztouch. Can't understand why it would be so unstable & crash so much.

Send me the .apk to test if you wish. Fred

Fred. I assume your user name is your e-mail address and have sent the apk to you. Thanks!

Nice app, three issues: 1. Need to allow GPS in core settings in control panel 2. Facebook screen causes app to lockup, see Wheel of Death in my how-to Buzztouch Process www.MySkylla.com 3. The share screen didn't work (perhaps because I'm using a tablet and not a phone. Fred

Hey, Thanks Fred! I already read about the wheel of death stuff. I will implement these changes right away and check the settings for the share screen. Do I then have to re-download and re-compile or are these changes automatically made to the app (and the user gets an update notice when they start it)? Also, did you see a splash screen with this image? http://thepaleochorasite.com/palappsplash.jpg Barry

Hi Barry, * The GPS setting does not require a recompile if the app is online. Users will pick that up in an update. * The Wheel of Death fix requires commenting out some Java code, which requires a recompile of the app. Basically, if you have to modify the actual Java code at all, you'll need to create a new apk. If all you are doing is making changes in the control panel, and your app is online, then users will pick up the updates automatically. Mark

Thanks, Mark! I will get on to the changes and compile my app v3.0. Hopefully it will then work as intended.

Yes, the Splash Screen looks nice. Fred

Thanks Fred

"Share this" plug in does not seem to want to work under any circumstances. I even changed from the SMS version to the E-mail version and I get the message in the emulator: Open with which App: No applications can perform this action. Is it normally buggy? Confusing. Also I have commented out the commands in the source code but IO still see the wheel in the emulator, although it does not hang. Is this normal?

@barryrodgers, Regarding your first issue, the share plugin will probably work fine on a real device, it's a stable plugin. The emulator won't have the correct packages installed - email client, sms etc. You should be able to set up an email address in the emulator, which will get the share with email working.

@Fred you mentioned earlier in this post about using html re direct as splash screen. I posted re this as an idea for a plugin a while back. i know how to create a html re direct but how do make it revert to main app screen after certain display time? would love to know this as its got great potential. thanks

Regarding, "but how do make it revert to main app screen after certain display time?" Not sure I understand this question. As I see it: App with Tabbed Layout Open app. The app displays the embedded html. (Splash Screen) After few seconds the screen redirects to another html (either embedded or online) online html screen with content. User continues using html doc, or User clicks on tab #2-#5 ***** Interesting possibility: Have embedded html only redirect you if you have not been redirected in the last "x" time frame. User opens app. Sees splash html. Is redirected. Uses the web2app button to return to app if html is online. Embedded app this time doesn't redirect. ***** Or instead of redirecting to online html use a multi-page embedded html doc. User opens app. Sees splash html. Is redirected to page 2. ***** Oh, the possibilities that localStorage open up. First time user opens app a EULA (or instructions page or "sign in" page or whatever page) is displayed. User clicks on I agree and page 2 is displayed. or User clicks on "decline" page 3 is displayed. When user reopens app using localStorage either page 2 or 3 is displayed. But it doesn't have to be page 2 or 3, it could be any page that's scripted. Fred

"after a few seconds the screen re directs to online html screen" how do i get to re direct again to online screen. sorry my question was a bit rubbish. as far as i have got before is set up html doc screen and set the url for the screen to a html redirect hosted on dropbox, the dropbox html redirects to a photo on photobucket. this is where i get lost!, after display of photo how do i get it to then redirect back again after a few seconds. hope this makes sense.

and set the url for the screen to a html redirect hosted on dropbox, the dropbox html redirects to a photo on photobucket. Sounds complicated. Why not just have first html redirect to photobucket. *** after display of photo how do i get it to then redirect back again after a few seconds. You can't. But you could just embed photo into the embedded html, Have photo display for 2 seconds then display page 3 or 5 or dynamically created page. Then you don't "have to redirect back" because you never left. Fred

think i get you now Fred. I know what you mean but a bit unsure how to embed a photo into the html. would it be something like im tags with an ahref to the photos location? unsure how i would code it directly to display for a few seconds

how to embed a photo into the html. would it be something like im tags with an ahref to the photos location? Yes, here's a iPad mini image embedded into the html. You could use link to embedded image or online image of the new iPad Mini (that's what I've done). <a href="http://m.cio.com/article/712579/iPad_Mini_What_We_Know_So_Far"><img title="ipad-mini.jpg" class="alignnone" alt="image" src="http://myskyllanotesmy.files.wordpress.com/2012/07/wpid-ipad-mini.jpg" /></a> ***** unsure how i would code it directly to display for a few seconds Haven't done this but dig out your redirect code and place internal page reference instead of external reference. A better solution would be to create the page dynamically and have it display for x seconds (please send me the code when you work it out). Fred

Thanks Fred. more info for me to chew on. I will try messing around a bit with some code when i get time. i was just interested in how i go about it. If i get some code going i will send it over no problem. thanks again.

Woohoo! My tester has reported that my first app is now running like a well oiled, eh, app. :) So, not having ever owned or used a smart phone or an app myself, I have some nitty gritty questions about distribution and installation. The app is for a small niche which frequent a website and FB page. This is where the main distribution will be. Q1. I don't have to put the app on Google Play if I don't want to, right? And I am still free to distribute it to Android users? Q2. What is the installation process. If I put my app on my site's hosting as this: www.mysite.com/myapp.apk will that install on a device when it is browsed to using the device? Or do I have to compress it for download and its then extracted on the device by the user? Q3. For offline awareness, a QR code box containing the direct link to the app would work, would it not?

Hi Barry, Q1 - Nope, you do not need to use Google Play, or any other market to distribute your app. You can market it any way you see fit. Q2 - All you need to do is post or email the apk you get out of Eclipse. Once a user clicks on the web link, or on the email attachment, it'll automatically start the download and install process. Q3 - Providing a QR code link to a URL that contains the apk would indeed work. Many people do that. Hope that helps! Mark

Great!. Thanks for the rapid response, Mark. Just want to say a big thank you to all who have helped and advised me on this thread. Hopefully, my app will work OK, be well used and popular amongst it's target audience. Then I may even start thinking about apple apps and start asking daft questions about that too.

Sweet! Good luck with it, and don't hesitate to post iOS questions. We can help there as well! Mark

Great. Just before i commit myself and get fliers printed, can anyone verify that this QR code works please? http://qr.kaywa.com/img.php?s=8&d=http%3A%2F%2Fgoo.gl%2F9E4xu

QR code works, nice app. From zero to a published app in 6 days! cool.

Thank you. Might have been easier if I owned a smart phone and knew more about apps from a user perspective. lol. But I have to again thank you guys here, as I was blundering around a bit.

Yeah, know what you mean. It's hard to visualize what it's going to look like and how it'll work. An emulator's ok but it's not the same as having the app working in your hand.