More information about me is available on my website. If you're into Twitter, you can follow me.
Theme by nostrich.
Text reblogged from nikf.org with 2 notes
A Thought
nikf:
With Apple now using some kind of static analysis tool to analyse applications submitted for App Store review, it’s had me thinking: why not let us test with it prior to submission - or have iTunes Connect immediately analyse upon uploading a binary? With it widely commented that the first 8 days of any review are to encourage developer self-moderation and bug discovery, the notion that developers have to wait 8 days for an automated process to run is - quite frankly - ridiculous.
As has been noted elsewhere, developers could indeed work around a desktop version that provides you with a hint of ‘You might want to fix these things’ when building a Distribution build, in an attempt to circumvent the analyser. However, if a developer were to receive an automated confirmation or warning within 24 hours of the initial application submission, it’d at least be a start.
Sidenote: Yes, developers can avoid the use of certain private frameworks (and undocumented methods in public frameworks), however we’re only human and honest mistakes can happen. This suggestion isn’t so much a way to work around deceptive attempts to contravene Apple’s (admittedly wolly, and continually fluid) App Store policies as it is a way to ensure that people who do make honest mistakes don’t wait 8 days to hear about it.
Even though I like the idea of having a tool to check my code for the usage of private API to avoid mistakes, I don’t really think that I need it that much. Unless if I’m using 3rd party code, I doubt that I will ever encounter the rejection problem because of using private API.
Apple themselves may need to think twice or more about giving out this tool to developers. There’s a potential for abuse, as there are few developers who didn’t gave up about violating some parts (no matter how small it’s) of the iPhone SDK agreement.
I still don’t like the inefficiencies and unfairness in the App Review process. But, in time I will just swallow it and move on, as it’s proven that there are some successful and good apps in the App Store without having these problems. I know that as a developer, we’re very accustomed to have full control of our work/code. In this case, we have to relinquish some of that “control” to enter the very popular mobile application distribution system, which is prone to misuse, mistakes and dishonest practice of various people that are using the system to gain money.
-
nevali liked this
-
jessearmand reblogged this from nikf and added:
Even though I like the idea...the usage of private API
-
nikf posted this
