I am wondering if anyone has comments to share about the submission to approval process you went through with Apple? I have my App finished. I registered with Apple Developer and paid the $99. I'm just wondering if everything else is a few simple steps, of a bit more complex than the web page guides we have access to, at basic steps in the process.

Hi @nickbaer, Here's a guide to submitting your app to iTunes : http://www.buzztouch.com/resources/Submitting_Your_App_To_iTunes_Connect_v1.0.pdf Overall it's relatively simple. The biggest part is signing your app with the Distribution Certificate. If you can nail that, then you're home free. Expect a wait of 5-7 days to get your app reviewed. Mark

Submission and iTunes Connect are fairly straight forward. There are several youtube videos that walk you through it. The approval process is a different animal. Once you submit you wait the 4-9 days for review and then it gets approved and all is great, or they reject it and give you a very generic reason and tell you to fix it and resubmit. Each time you resubmit you will have to wait the approval time (sometimes slightly shorter) Approval seems to be a very subjective approach based on the reviewer you get. Google ios app rejection, you wont believe the amount of responses. That said, my last app went through on the first try. Just depends on what your app does and who reviews it.

Great. I'm wondering if anyone has found any modified, or new steps, since this FAQ was written.

Is there one location for Android Apps, or more than one? I did get signed up with Amazon Developer, since I have a long-standing relationship with a couple of Amazon divisions.

No changes to the doc since I've written it. All info should still be good. Google Play and Amazon Market are the two major places for Android apps. Mark

I'm looking forward to making the Android version of the App I made for IOS. It's a Map App, and I used BT to create a 1 Country, 1 City, 1 Category menu structure, then modified the JSON (using a SQL CSV table and PHP scripting) to add 12 Countries, 100 cities, 4 Categories, 1 transparent background if it is Fair month... I'm holding my breath to find out if I go back to square one creating the Android version. I assume luck is not blowing in my direction that the JSON for IOS is not the ? for Android.

Well, the JSON is the same for both Android and iOS...it's just how the Java and Objective C files process it that's different. There are two issues that you face : (1) does the version of BT you are using support the same features (plugins) for both iOS and Andorid, and (2) does the app look as good in Android as it does in iOS. The answer to (2) is often no, and is what generally drives having to build two versions. Not much buzztouch can do about that fact. Mark

I'm preoccupied right now setting up Eclipse, and the nuisance, Windows-esg steps to get it and its components all installed. Am totally not impressed with this convoluted scheme.

Yeah, it's a total pain in the butt. I'm far more excited to develop for iOS than Android. Huge fragmentation in the Android market makes it very difficult to design anything! I wrote a guide to setting up the Android environment..it's in buzztouch.com/resources/. Feel free to contact me at MrkFleming at gmail dot com if you run into any problems! Mark

Hi Mark - Could you make a couple of edits to your http://www.buzztouch.com/resources/Submitting_Your_App_To_iTunes_Connect_v1.0.pdf ? The first has to do with this sentence: "There are basically two processes you need to go through in order to get your app into iTunes, and ultimately to your customers. First, you have to add your application to iTunes via the Apple Member Center." I'm not sure what the "Second" thing is. I couldn't find it using "Second". At this point in the document, could you list the two items, like as a table of contents, and a # <a>nchor link to both? In giving the document a first read through, I'm sensing there's a lot of work to be done in Xcode before I even sign in to Apple Developer. Perhaps then processes 1 & 2 (assuming #2 is Xcode steps) are in reverse order? I'm also having a problem with: 6 c. Bundle ID: An identifier used by iOS and Mac OS X to recognize any future updates to your app. Your Bundle ID must be registered with Apple and unique to your app. Bundle IDs are app-type specific (either iOS or Mac OS X). You should have created a Bundle ID earlier in your certificate generation process. I use a wildcard ID. This field should be populated with Bundle IDs that you created, so pick the appropriate one. Certificate generation process is not in the document, using those words to search on.

2 hours later, I got the App testing on my iPhone. Apple manual needs some work.

Hi @nickbear, Thanks for your comments on the doc. I'll review them and the doc, and make the appropriate changes. I should probably have specified at the start of the doc that it was assumed all the certificate stuff was taken care of...I don't even really broach that in this doc. The primary purpose was the process of putting together the record in iTunes, making sure the right stuff matched in Xocde, and then getting it done. In any event, I'll give it a look to see how I can make things better, without trying to write an entire manual on iOS development! Mark

https://developer.apple.com/library/ios/#documentation/ToolsLanguages/Conceptual/YourFirstAppStoreSubmission/ProvisionYourDevicesforDevelopment/ProvisionYourDevicesforDevelopment.html#//apple_ref/doc/uid/TP40011375-CH4-SW1 needs some help!!!! Shame on Apple!!!! Having grown with Macs since my first in 1986, I'm kind of used to the First > Second > Third method of describing items to click on. NOT: "A menu item appears (in the Code Signing Identity Build setting pop-up menu) for each provisioning profile your development certificate belongs to. The default setting is iPhone Developer in the Automatic Profile Selector menu, which matches your iOS Team Provisioning Profile developer certificate" upside down and nonsense. That not only took way to long, but the first try BROKE my original BT downloaded build, and I had to download a fresh one, and all of that.

Totally agree. The whole signing thing is absolutely ridiculous in how difficult and error prone it is. And that's not even talking about the times it just stops working for some unknown reason! I really try hard in my docs to do the 1, 2, 3 step thing, and I like to include as many screen shots as possible to make things more explanatory. Some topics are harder than other to stay with that recipe. Mark