Hey all - I'm done! As simple as Buzztouch is, I reckon I'm beaten now, just in getting the iTunes end of my app in, done and on the way to the app store. Never want to look up provisioning profiles again ever! Given I have no Android devices, and just don't want to have a go at learning another convoluted development system, would anyone like to compile and help me submit a final app off to Android land? Will pay! Message me with an estimate if you like.

It depends on what your app does. If it is solely based on Buzztouch concepts, there is a good chance for someone to "end" your app on Android. If, however, there is some iOS programming involved, it would probably be better to start anew on Android and rewrite it so that the both versions are similar if not quite the same.

Hey Dusko - It's all buzztouch - I use maps, and started down the road of getting an API for that etc etc - I want them to be identical so I can just do what I need to do from the bt panel as much as possible. I figure it's a reasonably straight ahead process of me send the apk, and images and docs and sounds. This aweosme person loads it up in Eclipse, does the maps api thing, icons, puts the files in the right place, has a quick look through the 15 or so buttons to see it works in the simulator, tries it on their phone (which I don;t own) and be done with it! I guess I really should do it myself in case I need to update it at some point But I'm sooo over it at the moment :-) Sooo over it! :-) Just want it done :-)

PM on the way! Mark

Quote: "But I'm sooo over it at the moment :-) Sooo over it! :-) Just want it done :-)" I'm sorry. I'm not laughing at you, I'm laughing with you. I know the feeling, lol! Cheers! -- Smug

Thanks Smug - appreciate the emapthy :-)

>I want them to be identical I don't think you can create an app for iOS and deploy it without changes to Android. In order to be as identical as possible, both apps would have to look into the same files on some kind of a server. That is easy to do with Buzztouch, just start using the Screen Data URL available in menu screens / plugins. (Of course, that would mean rewriting a good bit of your app in another way, but hey, at least that option will be available to you when you recover from the first try at building apps with Apple.) Then, there is the question of plugin inequality. There are many more plugins for iOS here than for Android. If you used those plugins, you are out of luck -- you will have to rewrite your Android app (almost) from scratch. Although you are tired at the moment, when you get the hang of working with Eclipse, it really becomes easy, if not downright dull. You just use it, and it makes no problems, at least that is how it is for me. It does become easier with practice (I've published 17 apps Android apps so far, so I speak from experience.) Hang on, just hang on, fail fast and then rise up again!

I agree with Dusko, "hang in there"...I did iOS first too, and was sort of dreading having to do it all over again with Android..but, I found plenty of quick help on these forums, the tutorials are great...when I finished it wasn't as bad as what I was dreading. One note of caution from one of your earlier posts "see if it works in their emulator, tries it on their phone...and be done with it" - there are hundreds of different Android device configs in terms of hardware, screen size, etc. - you can't cover them all of course, but if you only did one you might get bad feedback from other Android users. To help ensure no bad surprises when you publish your app, you might want to find a few friends with Android phones to be quick beta testers for you. When I did my apps last fall, I Googled "top Android phones 2013", found a list of 10, then asked friends if they'd be willing to load my app and just make sure it looks right and the buttons/plug-ins function as expected. This beta testing did uncover a couple of things (nothing critical, but I do remember tweaking the design based on their feedback).