What I learnt from my submission of CallSaver

[cornishGeeza]

Okay, since the dust has settled after CallSaver went live in the UK App Store, I thought I would share a few things that I learnt

1. Apple do not seem to do a user test. I did not get my server pinged the whole time they had it. I suspect that they are doing a Build and Analyze. So, do that too and get rid of all those Warnings.
2. I was nervous of leaving NSLogs and commented out code all over the place - they did not seem to mind. I suspect when the Distribution Binary is created, these are left out.
3. DO NOT put in any imagery of the iPhone - I was rejected for this schoolboy error. Cost me 12 days and lost income.
4. The position in the chart is difficult to work out, but I reckon it must be calculated on a rolling 2 day volume. My app was £1.79 so has a hard time competing against those at £0.59
5. Pricing. If your app can compete at a higher price point, do it. I figure there are less haters in this range and therefore ratings and reviews will be better.
6. Sales numbers on iTunes Connect come out 10.30ish for UK only and just after 11.00 if submitted in the US as well.
7. I rushed my App through, even though it took me 11 months to create. I think it is better to get it out there and update than hang on perfecting it. the feeling of relief when my first App was accepted was great because I now know that I can issue an update and it does not matter if it is rejected: I have an app making money
8. I am sometimes confused by the feedback data I am getting; my App is designed to provide alternative numbers for those prefixed 08. I am unable to get an idea if the user is getting a bad experience or not, so try and build in a way (if it is applicable to your type of App) to be able to analyse this.

I will add some more when I think of them.

I hope that help some of those less experienced members (like me!)

Jeremy

[BrianSlick]

Originally Posted by cornishGeeza

1. Apple do not seem to do a user test. I did not get my server pinged the whole time they had it. I suspect that they are doing a Build and Analyze. So, do that too and get rid of all those Warnings.

I've heard mixed results of this. I know of someone else who saw Apple testing the app via their analytics. I also received an email from a client that was from Apple showing the steps required to duplicate a crash. They clearly had used the app.

Originally Posted by cornishGeeza

2. I was nervous of leaving NSLogs and commented out code all over the place - they did not seem to mind. I suspect when the Distribution Binary is created, these are left out.

They won't inherently care, but if you leave too many logs active, you will see a performance hit. You should do something to disable them in your Release/Distribution configuration(s).