Need advice before submitting an iPhone app

[rdmiller]

I'm on the verge of submitting an iPhone/iPad app. All features are working, including in-app purchasing. This app has 3 versions: free, standard version, and a premium version.

I want to take advantage of promoting the app by offering free promo codes to reviewers. But I believe those codes can only be used to obtain a given app (whatever version it might be), but cannot be used to unlock features through in-app processes. Seems to me the only way around this is to submit to Apple 3 separate versions of my app:

- Free version, containing in-app purchase options to upgrade
- Standard version, containing an in-app purchase option to upgrade to the Premium version
- Premium version

With this approach, I can give reviewers promo codes for the Premium version.

Is this the best way to go?

Thanks.
Richard Miller

[FireWorx]

That's a great question. I wish I could help but have little experience with those features. I will have to remain on the sidelines.

I currently have two LC apps in the store and am preparing to submit my 3rd today. I am in a bit of a quagmire over the issue of upgrading to v5.5 or not before I submit. I guess if I want my app to run on IOS 5.1 i will have too? What version are you using?

Dave

[FireWorx]

I just upgraded my iPhone to 5.1 and then tested the apps I currently have in the iStore built with LC 5.02. They run fine on 5.1.

I think I am going to go ahead and submit this latest app (not yet store approved) under 5.02 but I would like to test it first on 5.1, the problem being I can't manually load it onto an OS 5.1 machine via Xcode 4.2 to test it.

Hmmm ... What to do?

Dave

[rdmiller]

Dave,

You can use AirLaunch to solve the issue. I believe it is $49, but it works great and makes it easy for others to test your app.

Richard

[CALL-151]

Richard, just a couple of potential issues with your plan.

1. Make sure your free version does enough to comply with Apple guidelines. If it's so crippled that users need to make a purchase to get basic functions, it will likely be rejected.
2. Think about the sequence in which you will submit your versions and what would happen if Apple approved one or two but not all three. You probably want to start with the premium version so you can get it approved and in the hands of reviewers, then follow with the other two.

[FireWorx]

I am taking a pause to consider the ramifications here. Would love to here Klaus, or Jaqueline, or Dix, or some of the other minds weigh in on this question.

If you were going to submit an app tomorrow with your LiveCode 5.02 and Xcode 4.2 and Profiles and Certificates all working well and your App doesn't seem to use or benefit from the upgrading to IOS 5.1.

1) Would you do the upgrade to 5.5 and Xcode 4.3 and then submit?
2) Do you think at some point the Apple Reviewers will reject Apps constructed and built with Xcode 4.2 for IOS 5.0. ?
3) Has the "do not back up folder attribute" been added to the LC v5.5 or do we have to purchase the external that is for sale via EXEMerge ?

Are there other considerations that I might not be seeing?

Dave

[jacque]

Since you asked...

1) Would you do the upgrade to 5.5 and Xcode 4.3 and then submit?

You don't have to, strictly speaking. The app will run on iOS 5.1. It won't take advantage of the new retina displays, but if you haven't coded for those then that probably doesn't matter. It will enlarge automatically to a semi-fuzzy bitmap, but will be workable.

2) Do you think at some point the Apple Reviewers will reject Apps constructed and built with Xcode 4.2 for IOS 5.0. ?

Yeah, probably, I bet. I vaguely recall something about that. I just heard third-hand that submissions must now include high-resolution splash screens and app icons. I expect the rest will follow shortly.

3) Has the "do not back up folder attribute" been added to the LC v5.5 or do we have to purchase the external that is for sale via EXEMerge ?

For now the external is your best bet, it isn't native to the engine yet. Alternately, if your data doesn't have to be permanent, put it in the cache folder. I've heard that if your data is text then it can go into Documents and be backed up. One person got a rejection for having a database file in Documents, but when he changed it to a text file the app was accepted.

I have just upgraded to Lion and XCode 4.3, mostly because I think I see the handwriting on the wall and there's no turning back. I did it with reluctance but it seems to be working okay.

Edited to add: AirLaunch does bypass XCode entirely, so yes, it works to move your existing app to a 5.1 device. I was using it that way for a few weeks until I updated to XCode 4.3.