Back in February of this year I developed a small Twitter app for iPhone called Chirpie Phentermine For Sale, . Frankly, Purchase Phentermine online no prescription, being a n00b in this area it was a little taxing, and that's just the development I'm talking about. What I was even less prepared for was the App Store approval process, purchase Phentermine online, so I thought I'd give some tips to developers hoping for a successful submission. Phentermine for sale,
Device Support
My first failure at App Store approval was because of device support. I had built in functionality that enabled the user to take a photo with the camera, or select a photo from their library and attach to a tweet, rx free Phentermine. It gave users the option to choose the source from a menu, Phentermine For Sale. Great times.
What I hadn't thought about, Phentermine samples, and should have realised throughout, was that an iPod Touch doesn't have a camera, yet they're given the same software and same camera option in my app, buy Phentermine online cod. This is made clear in the iPhone Human Interface Guidelines - Go over it with a fine tooth comb. Buy Phentermine online no prescription, Write code that validates the device/availability of hardware to support your software!
Don't Assume Reviewer knowledge of 3rd party products
So this was an interesting one. Like I said before, I was giving the option to attach photos, Phentermine over the counter, the device grabs an image, Buy Phentermine without prescription, compresses it and then uploads it to a third party service like Twitpic. Phentermine For Sale, As a regular Twitter iPhone app user I realised that I had to wait x amount of time for that to take place before I submitted the tweet, in order to let the upload finish and to get back a Twitpic URL. That assumption was clearly wrong. My app was again rejected because the reviewer didn't wait, buy cheap Phentermine, and classed that as a critical bug and against the sales description as the image wasn't attached, Phentermine pharmacy, assuming it was attached instantly.
Another rejection also came during a 1.x release, so after the app was in the store, online buy Phentermine without a prescription. The reviewer didn't have Facebook or Twitter credentials to use the application with, Where can i order Phentermine without prescription, therefore the app update was rejected.
So, do make sure any 3rd party integration credentials are supplied, and try not to assume any kind of user behaviour, Phentermine For Sale. (This should be a given, but as a regular iPhone user, online buying Phentermine, you may become dull to certain aspects). Buy Phentermine no prescription,
Email Apple to complain your app is taking too long
This was an interesting one. I could see my app was taking longer than other people's new submissions, and it bugged me that Chirpie was going nowhere, buy no prescription Phentermine online. So I emailed Apple to find out why. Phentermine For Sale, They replied within an hour, and the app went into review within a couple more. Buy cheap Phentermine no rx, The app was rejected ultimately for one of the issues above, but it worked.
Don't email Apple to complain your app is taking too long
The flipside to emailing Apple is that it usually does nothing for your cause, order Phentermine. During my prolonged initial 1.0 submission (and after my initial chaser email that seemed to speed up Apple), Buy Phentermine from mexico, I again email them as my app appeared to be stuck in limbo land again. This time Apple were less helpful and told me to wait like the rest, and that some apps take longer to go through than others, where can i find Phentermine online.
Point taken, I never emailed them again, Phentermine For Sale.
New apps take longer than Existing App updates to approve
Something you will quickly learn is that .x releases of your application will take a very short time, Where can i buy Phentermine online, usually 24 hours turn around. For new apps it's longer, how long is down to the size and complexity of your application, buy Phentermine from canada.
What would infuriate me is that I knew for certain that a developer had submitted his twitter app the exact same time as me (Feathers), Order Phentermine online c.o.d, had very similar functionality, and was approved within 2-3 days, vs mine which was stuck in limbo for 5 days until I got a response from Apple, buy Phentermine without a prescription.
Which leads me to my next point...
Existing "Trusted" Developers appear to be fast-tracked
Feathers developer @Aral Phentermine For Sale, had previously developed applications that were live in the store. Buy generic Phentermine, I can only summise that this fact gave him a kind of "trusted developer" status, which meant that his application could go through first submission a little easier than my noobie one.
I have no idea if this is true, buy generic Phentermine, but it's the only way I can understand why Feathers was approved really quickly for a 1.0 release, Where can i order Phentermine without prescription, and mine was stuck.
Memory Leaks don't matter
This was an unknown to me, I had assumed that my submissions should be 100% memory leak free, Phentermine samples. In actual fact, Purchase Phentermine online, this isn't true. Whilst it should be best practice for any developer to ensure they have no memory leaks in their code, you can happily submit your app (and get it approved) with memory leaks, Phentermine For Sale.
Conclusion
I hope this brief summary helps some developers with their submissions. Some of the mistakes above are easy to make - and shouldn't happen for seasoned pros, order Phentermine online c.o.d, but sometimes you have to make them to realise.
Feel free to add any of your own learnings to the App Store submission process in the comments section. I don't think this is against my NDA... we'll soon see.
Similar posts: Lunesta For Sale. Buy Noctamid Without Prescription. Where can i buy Valium online. Buy Ketazolam without prescription.
Trackbacks from: Phentermine For Sale. Phentermine For Sale. Phentermine For Sale. Phentermine For Sale. Phentermine For Sale. Online buy Phentermine without a prescription. Order Phentermine online c.o.d. Order Phentermine. Order Phentermine no prescription. Phentermine price. Phentermine price. Buy Phentermine online cod. Online buying Phentermine. Phentermine samples. Buy Phentermine without a prescription.
Similar Articles:
Chirpie 1.2 Available in the App Store
Chirpie for iPhone Released to the App Store
Chirpie 1.1 Available in the App Store
Using xAuth, an alternate OAuth from Twitter
Introducing Chirpie for iPhone
I am surprised at your Memory Leaks don’t matter comments, it seems best practice doesn’t always mean that
So, what did you have to change to get around the reviewer not waiting for the tinypic url to return?
@Techwatch – I guess that’s Apple’s call – they could opt to say no memory leaks 100%, but they would probably refuse a large proportion of the apps submitted.
@Edward – I had to stop the app from submitting the tweet until the upload had completed. The irony was, this supposed “bug” was present in the 1.0 release which Apple approved, but they failed it in a .x release. Guess it depends who you get to review…
It would be extremely hard for Apple to reject your app because of memory leaks. Without debugging symbols and the like, debugging your app or otherwise inspecting it is much more difficult. It’s not impossible, certainly, but since memory leaks will (at worst) simply kill your application when it consumes too much memory, the only one who stands to lose from memory leaks is you.
helpful information, I have yet to run the submission process but I will be attempting soon. thanks for the heads up.
Thanks steve for the information about the sumission process.
That’s useful, thanks for taking the time to post this Steve.
Thanks for this information. I’ve barely began development on my first app, but am looking early on for reasons my app might be rejected so I don’t design them in or fail to check.